Statistics for occurrence #1 of “Houston” in chapter 89, page 735 of Rebellion Record: a Diary of American Events: Documents and Narratives, Volume 9.:

...o Matagorda Bay, and which was also defended by strong and extensive fortifications, and a force of two thousand men,--artillery, cavalry, and infantry,--who could be reenforced in any emergency from Houston and Galveston. The troops were under command of Major-General C. C. Washburne, then commanding the thirteenth corps. Fort Esperanza was invested, and after a most gallant action the enemy blew up h...
Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
Houston (Mississippi, United States) 46 0 6 0 0 user votes
Houston (Louisiana, United States) 2 0 0 0 0 user votes
Houston (Alabama, United States) 1 0 1 0 0 user votes
Houston (Georgia, United States) 1 0 1 0 0 user votes
Houston (Alabama, United States) 0 0 0 0 0 user votes
Houston (Alaska, United States) 0 0 0 0 0 user votes
Houston (Arkansas, United States) 0 0 0 0 0 user votes
Houston (California, United States) 0 0 0 0 0 user votes
Houston (Canada) 0 0 0 0 0 user votes
Houston (Colorado, United States) 0 0 0 0 0 user votes
Houston (Delaware, United States) 0 0 0 0 0 user votes
Houston (Delaware, United States) 0 0 0 0 0 user votes
Houston (Florida, United States) 0 0 0 0 0 user votes
Houston (Idaho, United States) 0 0 0 0 0 user votes
Houston (Illinois, United States) 0 0 0 0 0 user votes
Houston (Indiana, United States) 0 0 0 0 0 user votes
Houston (Kentucky, United States) 0 0 0 0 0 user votes
Houston (Louisiana, United States) 0 0 0 0 0 user votes
Houston (Minnesota, United States) 0 0 0 0 0 user votes
Houston (Mississippi, United States) 0 0 0 0 0 user votes
Houston (Nebraska, United States) 0 0 0 0 0 user votes
Houston (North Carolina, United States) 0 0 0 0 0 user votes
Houston (North Carolina, United States) 0 0 0 0 0 user votes
Houston (Ohio, United States) 0 0 0 0 0 user votes
Houston (Pennsylvania, United States) 0 0 0 0 0 user votes
Houston (Tennessee, 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.