Statistics for occurrence #1 of “Pulaski” in chapter 11.109 of Southern Historical Society Papers, Volume 9.:
...ng and sad experience of retreating was now reversed, and we were going to redeem Tennessee and Kentucky, and the morale of the army was excellent.
We hoped to cut off a large body of Federals at Pulaski , but by a forced march they got into Columbia just in time to prevent capture.
On the 27th of November we formed around Columbia, the two wings of the army resting on Duck river, Cheatham being to ...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
|
Pulaski (Virginia, United States) |
47 |
0 |
3 |
0 |
0 user votes |
|
Pulaski (Kentucky, United States) |
34 |
0 |
8 |
0 |
0 user votes |
|
Pulaski (Georgia, United States) |
21 |
0 |
3 |
0 |
0 user votes |
|
Pulaski (New York, United States) |
5 |
0 |
1 |
0 |
0 user votes |
|
Pulaski (Missouri, United States) |
4 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Georgia, United States) |
3 |
0 |
3 |
0 |
0 user votes |
|
Pulaski (Arkansas, United States) |
2 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Indiana, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Pulaski (Ohio, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Pulaski (Virginia, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Pulaski (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Kentucky, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Oklahoma, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Pulaski (Wisconsin, 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.