Statistics for occurrence #1 of “Stark” in chapter 2 of Medford Historical Society Papers, Volume 3.:
...ynn, and Medford were given charge of this work, with authority to draw on the troops quartered in Medford as they might consider necessary.
This refers to the New Hampshire men under Sargent and Stark .
We have no positive record that the Medford company was under fire at the Battle of Bunker Hill, but we know that after the British landed their regiment was stationed in the road leading to Lec...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | John Stark | 121 | 9 | 7 | 1 | 0 user votes | |
Stark | 120 | 0 | 30 | 0 | 0 user votes | ||
A. Q. M. Stark | 20 | 0 | 0 | 0 | 0 user votes | ||
A. W. Stark | 15 | 0 | 1 | 0 | 0 user votes | ||
Molly Stark | 12 | 0 | 0 | 0 | 0 user votes | ||
Gustaf Stark | 7 | 0 | 1 | 0 | 0 user votes | ||
Benjamin Stark | 6 | 0 | 0 | 0 | 0 user votes | ||
Kirk Stark | 6 | 0 | 0 | 0 | 0 user votes | ||
William Stark | 6 | 0 | 0 | 0 | 0 user votes | ||
Alexander W. Stark | 5 | 0 | 3 | 0 | 0 user votes | ||
C. E. Stark | 4 | 0 | 2 | 0 | 0 user votes | ||
Daniel Stark | 4 | 0 | 0 | 0 | 0 user votes | ||
Mary Stark | 4 | 0 | 0 | 0 | 0 user votes | ||
Charles Stark | 3 | 0 | 1 | 0 | 0 user votes | ||
A. B. Stark | 2 | 0 | 2 | 0 | 0 user votes | ||
A. R. Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
Bolivar Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
George Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
Herman I. Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
Mollie Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
P. B. Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
Peter B. Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
Samuel Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
W. A. Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
W. F. Stark | 2 | 0 | 0 | 0 | 0 user votes | ||
Denton D. Stark | 1 | 0 | 1 | 0 | 0 user votes | ||
Henry Stark | 1 | 0 | 1 | 0 | 0 user votes | ||
T. B. Stark | 1 | 0 | 1 | 0 | 0 user votes | ||
W. H. Stark | 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.