Statistics for occurrence #1 of “Paris” in chapter 1.11 of Southern Historical Society Papers, Volume 19.:
...er, and in a straggling line passed by the Big Poplar Tree that crowns the summit and is the corner of four counties, Clarke, Warren, Fauquier and Loudoun.
Coming down the mountain by the hamlet of Paris , and there leaving the pike, we took the country road, soft and damp, to the railroad station of Piedmont, where, sleeping on the ground, we awaited the arrival of the train to carry us to Manassas J...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
† |
Paris (Virginia, United States) |
187 |
2 |
5 |
0 |
0 user votes |
|
Paris (France) |
475 |
0 |
37 |
0 |
0 user votes |
|
Paris (Arkansas, United States) |
16 |
0 |
0 |
0 |
0 user votes |
|
Paris (Canada) |
4 |
0 |
0 |
0 |
0 user votes |
|
Paris (Arkansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (California, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Idaho, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Maryland, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (New Hampshire, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (South Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Paris (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.