Statistics for occurrence #1 of “Frankfort” in chapter 109, page 180 of Rebellion Record: a Diary of American Events: Documents and Narratives, Volume 11.:
...on on Thursday last, under the impression that the war was over.
This impression was generally shared by the citizens of that place, and on application at the Provost-Marshal's office for a pass to Frankfort , I received the gratifying reply that none was required.
Yet, so little was known of the situation by the authorities, that Morgan's forces entered the city the night succeeding the very afternoon...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
† |
Frankfort (Kentucky, United States) |
880 |
46 |
110 |
2 |
0 user votes |
|
Frankfort (Missouri, United States) |
3 |
0 |
1 |
0 |
0 user votes |
|
Frankfort (Pennsylvania, United States) |
2 |
0 |
2 |
0 |
0 user votes |
|
Frankfort (Hesse, Germany) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Maine, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Missouri, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (New Jersey, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (New Mexico, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (New York, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Oklahoma, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (South Africa) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (South Dakota, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Tennessee, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Frankfort (Washington, 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.