Statistics for occurrence #1 of “Moorman” in chapter 4 of Maj. Jed. Hotchkiss, Confederate Military History, a library of Confederate States Military History: Volume 3, Virginia:
...ld not relieve them from any liabilities incurred by taking up arms against the United States.
Pegram accepted the terms offered, but when he formed his companies to march to Beverly, he found that Moorman and his forty brave mountaineers had left during the night, taking the Seneca road, as he had proposed.
These in due time reached Monterey, as could all of Pegram's command had he boldly pushed for...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | J. B. Moorman | 7 | 7 | 1 | 1 | 0 user votes | |
Moorman | 93 | 0 | 33 | 0 | 0 user votes | ||
M. N. Moorman | 40 | 0 | 6 | 0 | 0 user votes | ||
George Moorman | 19 | 0 | 9 | 0 | 0 user votes | ||
Marcellus N. Moorman | 17 | 0 | 3 | 0 | 0 user votes | ||
Robert Moorman | 10 | 0 | 2 | 0 | 0 user votes | ||
C. H. Moorman | 8 | 0 | 0 | 0 | 0 user votes | ||
S. T. Moorman | 8 | 0 | 0 | 0 | 0 user votes | ||
Charles Moorman | 4 | 0 | 0 | 0 | 0 user votes | ||
R. B. Moorman | 4 | 0 | 0 | 0 | 0 user votes | ||
Edward H. Moorman | 2 | 0 | 2 | 0 | 0 user votes | ||
Jerry Moorman | 2 | 0 | 0 | 0 | 0 user votes | ||
Marcellus Moorman | 2 | 0 | 2 | 0 | 0 user votes | ||
S. I. Moorman | 2 | 0 | 0 | 0 | 0 user votes | ||
S. L. Moorman | 2 | 0 | 0 | 0 | 0 user votes | ||
Samuel Moorman | 2 | 0 | 0 | 0 | 0 user votes | ||
T. S. Moorman | 2 | 0 | 0 | 0 | 0 user votes | ||
Achilles H. Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
Bob Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
E. G. Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
J. J. Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
Jonathan B. Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
Jonathan J. Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
Marceline Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
Robert B. Moorman | 1 | 0 | 1 | 0 | 0 user votes | ||
Samuel A. Moorman | 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.