Statistics for occurrence #1 of “Reagan” in article pos=21 of The Daily Dispatch: January 4, 1864., [Electronic resource]:
...ably to demand satisfaction, for which they were soon after arrested and held to bail to answer before the Mayor at 10 o'clock Saturday morning. Before the hour of trial Baldwin secured the arrest of Reagan as a conscript, and thus prevented his appearance at the hour appointed.
Reagan and Baldwin have been, and probably are now, Government contractors, but not citizens of the Confederacy.
Reaga...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Hugh Reagan | 19 | 16 | 1 | 0 | 0 user votes | |
John H. Reagan | 389 | 0 | 31 | 0 | 0 user votes | ||
Reagan | 90 | 0 | 42 | 0 | 0 user votes | ||
J. H. Reagan | 34 | 0 | 2 | 0 | 0 user votes | ||
John Henninger Reagan | 28 | 0 | 4 | 0 | 0 user votes | ||
John Reagan | 12 | 0 | 0 | 0 | 0 user votes | ||
W. B. L. Reagan | 8 | 0 | 2 | 0 | 0 user votes | ||
Christopher Reagan | 6 | 0 | 0 | 0 | 0 user votes | ||
Hugh R. Reagan | 4 | 0 | 0 | 0 | 0 user votes | ||
J. J. Reagan | 4 | 0 | 0 | 0 | 0 user votes | ||
James B. Reagan | 4 | 0 | 0 | 0 | 0 user votes | ||
John A. Reagan | 4 | 0 | 0 | 0 | 0 user votes | ||
Peter Reagan | 4 | 0 | 0 | 0 | 0 user votes | ||
H. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
H. C. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
H. W. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Hugh L. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Hught Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
J. C. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Jerry Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Joseph Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Lt Robert Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
M. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Monteith Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
R. Reagan | 2 | 0 | 0 | 0 | 0 user votes | ||
Judge Reagan | 1 | 0 | 1 | 0 | 0 user votes | ||
Richard C. Reagan | 1 | 0 | 1 | 0 | 0 user votes | ||
William Reagan | 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.