Statistics for occurrence #1 of “Taylorsville” in chapter 145 of Rebellion Record: a Diary of American Events: Documents and Narratives, Volume 8.:
... and returned in safety.
The main command, just at nightfall, Monday, moved forward and during the night crossed the South-Anna River.
Here the advance had a skirmish with an infantry picket near Taylorsville , and dispersed them.
The men crossed, a brief halt was made to feed, when the column at daylight moved on to Richmond, before which, and within the second line of defences, a position was taken at...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
† |
Taylorsville (Virginia, United States) |
64 |
4 |
2 |
0 |
0 user votes |
|
Taylorsville (Tennessee, United States) |
9 |
0 |
1 |
0 |
0 user votes |
|
Taylorsville (Arkansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (California, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Georgia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Maryland, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Maryland, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Mississippi, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Texas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Taylorsville (Utah, 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.