Statistics for occurrence #1 of “Pulaski” in chapter 9 of John M. Schofield, Forty-six years in the Army:
...s a department commander, and a copy of instructions which had already been telegraphed to General Stanley at Pulaski.
I assumed command in the morning of November 14.
The moment I met Stanley at Pulaski , in the evening of November 13, he called my attention to the faulty position of the troops and to an error in General Thomas's instructions, about which I then knew nothing because I was unacquaint...
|
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.