Statistics for occurrence #1 of “Paris” in chapter 31, page 324 of William Hepworth Dixon, White Conquest: Volume 2:
...er was not easy to arrange.
Monsieur St. Jean sailed for France, where he asserted he could do the settlers service.
So they called their place St. Jean.
But when the fussy little consul got to Paris , he found people too busy with their revolution to pay much attention to the graziers and bushmen on Sleeper's Creek.
Thinking the consul false, the Scots changed their name to St. Johns.
But the...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
|
Paris (France) |
475 |
0 |
37 |
0 |
0 user votes |
|
Paris (Virginia, United States) |
187 |
0 |
5 |
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.