Statistics for occurrence #1 of “Ivy Creek” in chapter 3 of Col. J. Stoddard Johnston, Confederate Military History, a library of Confederate States Military History: Volume 9.1, Kentucky:
...roops under General Nelson.
On the 8th of November, while Colonel Williams was at Piketon, General Nelson advanced, when after a skirmish of his advance guard Williams occupied a mountain defile at Ivy Creek , fifteen miles in advance of Piketon.
Next day the enemy advanced in heavy force and dislodged Capt. A. J. May, who with several hundred men, attempted to hold the pass.
Colonel Williams in his r...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
| † |
Ivy Creek (Kentucky, United States) |
26 |
2 |
0 |
0 |
0 user votes |
|
Ivy Creek (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Alabama, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Alaska, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Colorado, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Georgia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
| † |
Ivy Creek (Kentucky, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Virginia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy creek (Virginia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Virginia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (West Virginia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Ivy Creek (Wyoming, 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.