Statistics for occurrence #1 of “Hosmer” in chapter 25, page 589 of Lucius R. Paige, History of Cambridge, Massachusetts, 1630-1877, with a genealogical register:

...y distinguished. Hopkins, John, in 1635 res. at the northwesterly corner of Dunster and Mount Auburn streets. He rem. in 1636 to Hartford, where he was Selectman in 1640, and Juror in 1643. Hosmer , Thomas, in 1635 res. on the southerly side of Brattle Street, and in 1642 on the southerly side of Winthrop Street, between Brighton and Spring streets. He was Selectman, or Townsman, 1635, and rem....
Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
† Thomas Hosmer 22 22 0 0 0 user votes
Harriet G. Hosmer 66 0 0 0 0 user votes
H. G. Hosmer 32 0 0 0 0 user votes
Hosmer 27 0 11 0 0 user votes
Harriet Hosmer 19 0 1 0 0 user votes
John Hosmer 16 0 4 0 0 user votes
James K. Hosmer 10 0 0 0 0 user votes
Horatio H. Hosmer 8 0 0 0 0 user votes
Joseph Hosmer 7 2 1 0 0 user votes
Addison Augustus Hosmer 6 0 0 0 0 user votes
Charles A. Hosmer 6 0 0 0 0 user votes
Leonard T. Hosmer 6 0 0 0 0 user votes
W. H. C. Hosmer 6 0 0 0 0 user votes
Alfred Hosmer 5 0 1 0 0 user votes
Charles E. Hosmer 4 0 0 0 0 user votes
F. E. Hosmer 4 0 0 0 0 user votes
Francis E. Hosmer 4 0 0 0 0 user votes
Henry Hosmer 4 0 0 0 0 user votes
John Edward Hosmer 4 0 0 0 0 user votes
Rufus Hosmer 4 0 0 0 0 user votes
William Hosmer 4 0 0 0 0 user votes
J. K. Hosmer 3 0 1 0 0 user votes
Abner Hosmer 2 0 0 0 0 user votes
Attest J. Hosmer 2 0 0 0 0 user votes
George Hosmer 2 0 0 0 0 user votes
Hattie Hosmer 2 0 0 0 0 user votes
Henry Cuyler Hosmer 2 0 0 0 0 user votes
James Kendall Hosmer 2 0 0 0 0 user votes
James Prescott Joseph Hosmer 2 0 0 0 0 user votes
Luther C. Hosmer 2 0 0 0 0 user votes
Martha Hosmer 2 0 0 0 0 user votes
P. E. Hosmer 2 0 0 0 0 user votes
William H. C. Hosmer 2 0 0 0 0 user votes
Zelotes Hosmer 2 0 0 0 0 user votes
Frederick C. Hosmer 1 0 1 0 0 user votes
Horace M. Hosmer 1 0 1 0 0 user votes
Marion Hosmer 1 0 1 0 0 user votes
Martha J. Hosmer 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.