Statistics for occurrence #1 of “Augusta” in chapter 1.30 of Southern Historical Society Papers, Volume 17.:
...rtion of their artillery and pursued the retiring troops as far as was consistent with our orders as rear guard.
With high respect,
Your obedient servant, J. Longstreet.
Col. Salem Dutcher, Augusta , Ga.:
Dear Sir, —My recollection of the battle of Williamsburg agrees substantially with your statement.
It was certainly not a drawn battle, as we took the enemy's position and his guns ...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
† |
Augusta (Georgia, United States) |
3,296 |
18 |
410 |
6 |
0 user votes |
|
Augusta (Kentucky, United States) |
27 |
0 |
13 |
0 |
0 user votes |
|
Augusta (West Virginia, United States) |
24 |
0 |
2 |
0 |
0 user votes |
|
Augusta |
10 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Indiana, United States) |
1 |
0 |
1 |
0 |
0 user votes |
|
Augusta (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Italy) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Louisiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Louisiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Maryland, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Minnesota, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Missouri, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Montana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (New Jersey, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Ohio, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Turkey) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (Western Australia, Australia) |
0 |
0 |
0 |
0 |
0 user votes |
|
Augusta (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.