Statistics for occurrence #1 of “McGowan” in chapter 1.1 of Southern Historical Society Papers, Volume 25.:
...ces of the enemy's artillery until thrice ordered to retreat.
We fell back again to the parapet at Hatcher's Run, rested the 30th there, and on the 31st again were ordered to fall in on the left of McGowan 's Brigade and charge the enemy.
The 59th were left to guard the trenches, and the 26th, 34th and 46th went into the charge.
They, with McGowan's Brigade, did good execution in staggering the over...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Samuel McGowan | 238 | 13 | 26 | 1 | 0 user votes | |
McGowan | 273 | 0 | 51 | 0 | 0 user votes | ||
S. McGowan | 113 | 0 | 5 | 0 | 0 user votes | ||
John McGowan | 57 | 0 | 5 | 0 | 0 user votes | ||
S. C. McGowan | 28 | 0 | 0 | 0 | 0 user votes | ||
Patrick McGowan | 22 | 0 | 0 | 0 | 0 user votes | ||
George McGowan | 16 | 0 | 0 | 0 | 0 user votes | ||
J. McGowan | 14 | 0 | 0 | 0 | 0 user votes | ||
J. E. McGowan | 9 | 0 | 1 | 0 | 0 user votes | ||
Gen S. McGowan | 8 | 0 | 0 | 0 | 0 user votes | ||
Alden T. McGowan | 6 | 0 | 0 | 0 | 0 user votes | ||
Pat McGowan | 6 | 0 | 0 | 0 | 0 user votes | ||
William A. McGowan | 6 | 0 | 0 | 0 | 0 user votes | ||
John R. McGowan | 4 | 0 | 0 | 0 | 0 user votes | ||
Ned McGowan | 4 | 0 | 0 | 0 | 0 user votes | ||
James McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
John J. McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
John W. McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
Martin McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
R. W. McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
Rodney W. McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
Thomas J. McGowan | 2 | 0 | 0 | 0 | 0 user votes | ||
— Mcgowan | 2 | 0 | 0 | 0 | 0 user votes | ||
H. McGowan | 1 | 0 | 1 | 0 | 0 user votes | ||
Homer McGowan | 1 | 0 | 1 | 0 | 0 user votes | ||
J. H. McGowan | 1 | 0 | 1 | 0 | 0 user votes | ||
John F. McGowan | 1 | 0 | 1 | 0 | 0 user votes | ||
Robert McGowan | 1 | 0 | 1 | 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.