Statistics for occurrence #1 of “Columbus” in chapter 124 of Rebellion Record: a Diary of American Events: Documents and Narratives, Volume 4.:
...e repulsed the gunboat fleet at New-Madrid.
A rebel transport, loaded with cannon, reported sunk by the fire from the fleet.
March 19.--Commodore Foote reports the island harder to conquer than Columbus .
Firing continued night and day.
March 20.--Cannonading continued all day. All the guns but one in the upper battery reported dismounted.
Hollins's ram sent from Memphis.
March 21.--Firin...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
|
Columbus (Georgia, United States) |
419 |
0 |
283 |
0 |
0 user votes |
|
Columbus (Mississippi, United States) |
325 |
1 |
141 |
1 |
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.