Statistics for occurrence #1 of “Windsor” in chapter 2, page 43 of Charles A. Nelson , A. M., Waltham, past, present and its industries, with an historical sketch of Watertown from its settlement in 1630 to the incorporation of Waltham, January 15, 1739.:

... Windsor
John Mason. May 10, 1637, Mason, with all his levy, and seventy friendly Indians under the command of Uncas, a Mohegan chief, taki...
Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
Windsor (Massachusetts, United States) 47 6 3 0 0 user votes
Windsor (United Kingdom) 47 0 1 0 0 user votes
Windsor (Canada) 27 0 3 0 0 user votes
Windsor (Canada) 19 0 9 0 0 user votes
Windsor (Virginia, United States) 13 0 1 0 0 user votes
Windsor (North Carolina, United States) 2 0 0 0 0 user votes
Windsor (Illinois, United States) 1 0 1 0 0 user votes
Windsor (California, United States) 0 0 0 0 0 user votes
Windsor (Canada) 0 0 0 0 0 user votes
Windsor (Canada) 0 0 0 0 0 user votes
Windsor (Florida, United States) 0 0 0 0 0 user votes
Windsor (Georgia, United States) 0 0 0 0 0 user votes
Windsor (Indiana, United States) 0 0 0 0 0 user votes
Windsor (Kentucky, United States) 0 0 0 0 0 user votes
Windsor (Louisiana, United States) 0 0 0 0 0 user votes
Windsor (Maine, United States) 0 0 0 0 0 user votes
Windsor (New Jersey, United States) 0 0 0 0 0 user votes
Windsor (New South Wales, Australia) 0 0 0 0 0 user votes
Windsor (New York, United States) 0 0 0 0 0 user votes
Windsor (North Dakota, United States) 0 0 0 0 0 user votes
Windsor (Ohio, United States) 0 0 0 0 0 user votes
Windsor (Ohio, United States) 0 0 0 0 0 user votes
Windsor (Ohio, United States) 0 0 0 0 0 user votes
Windsor (Ohio, United States) 0 0 0 0 0 user votes
Windsor (Ohio, United States) 0 0 0 0 0 user votes
Windsor (Pennsylvania, United States) 0 0 0 0 0 user votes
Windsor (South Australia, Australia) 0 0 0 0 0 user votes
Windsor (South Carolina, United States) 0 0 0 0 0 user votes
Windsor (Texas, United States) 0 0 0 0 0 user votes
Windsor (Vermont, United States) 0 0 0 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.