Statistics for occurrence #1 of “Cairo” in entry fremont-john-charles of Harper's Encyclopedia of United States History:
...ny of the home guards.
He strongly fortified St. Louis, and prepared to place the important post at Cairo in a position of absolute security.
With nearly 4,000 troops on steamers, he proceeded to Cairo with such a display that the impression was general that lie had 12,000.
Although large bodies of Confederate troops in Kentucky and Missouri were gathered for the purpose of seizing Cairo and Bird...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
|
Cairo (Egypt) |
183 |
14 |
7 |
4 |
0 user votes |
|
Cairo (Missouri, United States) |
5 |
0 |
1 |
0 |
0 user votes |
|
Cairo (Alabama, United States) |
2 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Kentucky, United States) |
2 |
0 |
0 |
0 |
0 user votes |
|
Cairo (West Virginia, United States) |
2 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Arkansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Egypt) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Florida, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Georgia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Nebraska, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Oklahoma, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (Tennessee, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Cairo (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.