Statistics for occurrence #1 of “Trenton” in chapter 45, page 227 of Rebellion Record: a Diary of American Events: Documents and Narratives, Volume 7.:
...o, of Negley's division, went to the top of Lookout Mountain beyond Paine's Mills; met the enemy's pickets, and dispersed them.
The head of Brannan's division reached Lookout Valley two miles below Trenton .
Reynolds's division in camp at Trenton.
Rumors of the enemy's design to evacuate Chattanooga.
Corps headquarters at Brown's Spring.
September 7.--Baird's division closed up with Negley's i...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
|
Trenton (Kentucky, United States) |
66 |
2 |
66 |
2 |
0 user votes |
|
Trenton (Alabama, United States) |
5 |
0 |
1 |
0 |
0 user votes |
|
Trenton (Canada) |
5 |
0 |
1 |
0 |
0 user votes |
|
Trenton (Arkansas, United States) |
4 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Michigan, United States) |
4 |
0 |
0 |
0 |
0 user votes |
|
Trenton (California, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Canada) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Florida, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Louisiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Maryland, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Nebraska, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (New Mexico, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (North Dakota, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Texas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (Utah, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Trenton (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.