Statistics for occurrence #1 of “Parkhurst” in chapter 1, page 18 of Historic leaves, volume 7, April, 1908 - January, 1909:
...e 2, 1865; died in Cambridge November 19, 1875.
Paine, Jeremiah T., died in hospital October 13, 1863.
Palmer, William D., promoted to corporal; to sergeant; killed in battle May 8, 1864.
Parkhurst , Melville C., went out as corporal; promoted to second lieutenant, Company B (Roxbury), September 8, 1864; to first lieutenant January 15, 1865; commissioned captain Company B June 7, 1865; Chief of ...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Melville C. Parkhurst | 12 | 7 | 2 | 1 | 0 user votes | |
Parkhurst | 25 | 0 | 17 | 0 | 0 user votes | ||
J. G. Parkhurst | 12 | 0 | 4 | 0 | 0 user votes | ||
C. Parkhurst | 8 | 0 | 0 | 0 | 0 user votes | ||
Charles Henry Parkhurst | 7 | 0 | 1 | 0 | 0 user votes | ||
John G. Parkhurst | 6 | 0 | 4 | 0 | 0 user votes | ||
Jonathan Parkhurst | 6 | 0 | 0 | 0 | 0 user votes | ||
Thomas H. Parkhurst | 6 | 0 | 0 | 0 | 0 user votes | ||
W. L. Parkhurst | 6 | 0 | 0 | 0 | 0 user votes | ||
Abraham Parkhurst | 4 | 0 | 0 | 0 | 0 user votes | ||
Matthew M. Parkhurst | 4 | 0 | 0 | 0 | 0 user votes | ||
Samuel Parkhurst | 4 | 0 | 0 | 0 | 0 user votes | ||
Veranus P. Parkhurst | 4 | 0 | 0 | 0 | 0 user votes | ||
W. E. Parkhurst | 4 | 0 | 0 | 0 | 0 user votes | ||
Clara B. Parkhurst | 3 | 0 | 1 | 0 | 0 user votes | ||
Daniel Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
George Samuel Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
Henry Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
Henry M. Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
J. M. Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
John Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
Lewis Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
Melvin C. Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
Nye Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
Sherman W. Parkhurst | 2 | 0 | 0 | 0 | 0 user votes | ||
V. V. Parkhurst | 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.