Statistics for occurrence #1 of “Pulaski” in chapter 15 of John M. Schofield, Forty-six years in the Army:
...ield to leave a sufficiently strong force for the defense of that point, and with the balance of his command proceed to carry out the instructions already given him, viz., to join the Fourth Corps at Pulaski , and assume command of all the troops in the vicinity, watch the movements of Hood, and retard his advance into Tennessee as much as possible, without risking a general engagement, until Maj.-Gen. A....
|
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.