Statistics for occurrence #1 of “Pulaski” in article pos=2 of The Daily Dispatch: October 4, 1864., [Electronic resource]:
...morning at Russell's hill, fourteen miles north of Gordonsville.
It is supposed that the object of this movement is a raid upon the Central railroad.
General Forrest reports, from near Pulaski , Tennessee, September 27th, that he succeeded the day before in capturing four trestles, three block houses and the fort at Elk Ridge, with about fifty prisoners, without the loss of a man, and had ...
|
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.