Statistics for occurrence #1 of “Pulaski” in chapter 1.31 of Southern Historical Society Papers, Volume 31.:
...Pocahontas; C. G. Paul, Harrisonburg; L. W. Sydnor, Staunton; J. R. Taylor, Fredericksburg; M. Campbell, Amherst; H. E. McCreedy, Roanoke; J. P. Wilkinson, Nebletts Van, Lunenburg county; W. P. Tate, Pulaski ; R. C. Barrett, Smithfield; G. M. Harrison, Fredericksburg; H. F. Carr, Newport News; H. A. Tabb, Gloucester county.
Cadets at large—Irving Boaz, Albemarle; T. H. Roseter, Norfolk; W. A. Dunl...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
|
Pulaski (Virginia, United States) |
47 |
2 |
3 |
0 |
0 user votes |
|
Pulaski (Kentucky, United States) |
34 |
2 |
8 |
2 |
0 user votes |
|
Pulaski (Georgia, United States) |
21 |
4 |
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.