Statistics for occurrence #1 of “Halsey” in chapter 1.55 of Southern Historical Society Papers, Volume 31.:
..., Major, Thornton, 17.
Hardee, Major-General W. J., 151.
Hardin, Major M. D., 141.
Hare, Otway P., 19.
Hare's Hill, 19.
Hallock, Chas., 86.
Halsey, Captain Don P., gallantry of 193, 200.
Halsey . Hon. Don P., 81,193.
Hancock, General W. S., 356.
Handkerchiefs, Battle of, 340.
Harpers Ferry, 32; capture of, 278.
Harris, Governor Isham G., 52.
Harrison, Miss, Ellanetta, 169.
...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Don Peters Halsey | 22 | 22 | 12 | 12 | 0 user votes | |
Halsey | 37 | 0 | 5 | 0 | 0 user votes | ||
D. P. Halsey | 27 | 10 | 11 | 0 | 0 user votes | ||
Don P. Halsey | 14 | 14 | 0 | 0 | 0 user votes | ||
Robert Halsey | 12 | 0 | 0 | 0 | 0 user votes | ||
Thomas Frederick Halsey | 12 | 12 | 0 | 0 | 0 user votes | ||
E. L. Halsey | 11 | 0 | 3 | 0 | 0 user votes | ||
James Halsey | 10 | 0 | 0 | 0 | 0 user votes | ||
C. S. Halsey | 8 | 0 | 0 | 0 | 0 user votes | ||
Edwin Lindsley Halsey | 7 | 0 | 3 | 0 | 0 user votes | ||
James M. Halsey | 7 | 0 | 1 | 0 | 0 user votes | ||
Colonel D. Halsey | 6 | 0 | 0 | 0 | 0 user votes | ||
Thomas Halsey | 6 | 2 | 0 | 0 | 0 user votes | ||
William Halsey | 6 | 2 | 0 | 0 | 0 user votes | ||
Seth Halsey | 5 | 2 | 1 | 0 | 0 user votes | ||
A. O. Halsey | 4 | 0 | 0 | 0 | 0 user votes | ||
Don Halsey | 4 | 4 | 0 | 0 | 0 user votes | ||
John Halsey | 4 | 2 | 0 | 0 | 0 user votes | ||
Stephen Halsey | 3 | 0 | 1 | 0 | 0 user votes | ||
A. P. Halsey | 2 | 0 | 0 | 0 | 0 user votes | ||
George Halsey | 2 | 0 | 0 | 0 | 0 user votes | ||
Julia D. B. Halsey | 2 | 2 | 0 | 0 | 0 user votes | ||
P. Halsey | 2 | 0 | 0 | 0 | 0 user votes | ||
William G. Halsey | 2 | 0 | 0 | 0 | 0 user votes | ||
Benjamin F. Halsey | 1 | 0 | 1 | 0 | 0 user votes | ||
Charles B. Halsey | 1 | 0 | 1 | 0 | 0 user votes | ||
J. P. Halsey | 1 | 0 | 1 | 0 | 0 user votes | ||
Stephen P. Halsey | 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.