Statistics for occurrence #1 of “Montgomery” in chapter 1.1 of Southern Historical Society Papers, Volume 37.:

...y the necessity for negotiating their transfer to the custody of the Confederacy. The first steps towards provision for ordnance needs were taken by the Confederate government while it was still at Montgomery , Ala. Col. (afterwards Genl.) Josiah Gorgas, who had been an ordnance officer in the U. S. army, was commissioned as Chief of the Ordnance Bureau, and near the end of February, 1861, Capt. (afterward...

Don't like any of these choices? Suggest a new possibility...

Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
Montgomery (Alabama, United States) 2,463 5 395 1 0 user votes
Montgomery (Tennessee, United States) 4 0 2 0 0 user votes
Montgomery (Kentucky, United States) 2 0 0 0 0 user votes
Montgomery (Massachusetts, United States) 2 0 0 0 0 user votes
Montgomery (Virginia, United States) 2 0 2 0 0 user votes
Montgomery (Texas, United States) 1 0 1 0 0 user votes
Montgomery (California, United States) 0 0 0 0 0 user votes
Montgomery (Illinois, United States) 0 0 0 0 0 user votes
Montgomery (Indiana, United States) 0 0 0 0 0 user votes
Montgomery (Iowa, United States) 0 0 0 0 0 user votes
Montgomery (Michigan, United States) 0 0 0 0 0 user votes
Montgomery (Minnesota, United States) 0 0 0 0 0 user votes
Montgomery (Mississippi, United States) 0 0 0 0 0 user votes
Montgomery (Mississippi, United States) 0 0 0 0 0 user votes
Montgomery (Nevada, United States) 0 0 0 0 0 user votes
Montgomery (New Jersey, United States) 0 0 0 0 0 user votes
Montgomery (Ohio, United States) 0 0 0 0 0 user votes
Montgomery (Ohio, United States) 0 0 0 0 0 user votes
Montgomery (Pennsylvania, United States) 0 0 0 0 0 user votes
Montgomery (South Carolina, United States) 0 0 0 0 0 user votes
Montgomery (Tennessee, United States) 0 0 0 0 0 user votes
Montgomery (Texas, United States) 0 0 0 0 0 user votes
Montgomery (United Kingdom) 0 0 0 0 0 user votes
Montgomery (West Virginia, United States) 0 0 0 0 0 user votes

† This entity has been selected by the automated classifier as the most likely match in this context. It may or may not be the correct match.