Statistics for occurrence #1 of “Frankfort” in chapter 1.1 of Robert Underwood Johnson, Clarence Clough Buell, Battles and Leaders of the Civil War. Volume 3.:
...nding McCown's division from Tupelo to Chattanooga, and again in August by sending the brigades of Cleburne and Preston Smith from Chattanooga to Knoxville;
and again, when Smith was pressed at Frankfort , that Bragg reenforced him promptly with one of his best divisions.
That Kirby Smith would, at any time, have been as ready and prompt to give Bragg any part or all of his army there can be no doub...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
† |
Frankfort (Kentucky, United States) |
880 |
46 |
110 |
0 |
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.