Statistics for occurrence #1 of “Columbus” in chapter 19 of Benson J. Lossing, Pictorial Field Book of the Civil War. Volume 3.:
... musketry, was made.
They pushed through abatis that covered the works, and pressed back the Confederates.
Two companies of the Tenth Missouri then seized another and perfect bridge, leading into Columbus , when Upton made another charge, sweeping every thing before him, and captured the city, twelve hundred men, fifty-two field guns in position, and large quantities of small-arms and stores.
He lost...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
† |
Columbus (Mississippi, United States) |
325 |
25 |
141 |
3 |
0 user votes |
|
Columbus (Georgia, United States) |
419 |
0 |
283 |
0 |
0 user votes |
|
Columbus (Alabama, United States) |
4 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Indiana, United States) |
3 |
0 |
3 |
0 |
0 user votes |
|
Columbus (Arkansas, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Columbus (New York, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Columbus (North Carolina, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Columbus (Colorado, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Georgia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Illinois, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Louisiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Montana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Nevada, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (New Jersey, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (New Mexico, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (North Dakota, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Columbus (Pennsylvania, 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.