Statistics for occurrence #1 of “Wakefield” in chapter 19 of HISTORY OF THE TOWN OF MEDFORD, Middlesex County, Massachusetts, FROM ITS FIRST SETTLEMENT, IN 1630, TO THE PRESENT TIME, 1855.:
...gue, 1763; Stocker, 1763; Storer, 1748.
Tebodo, 1757; Teel, 1760; Tidd, 1746; Tilton, 1764; Tompson, 1718; Trowbridge, 1787; Turner, 1729; Tuttle, 1729; Tyzick, 1785.
Wait, 1725; Waite, 1785; Wakefield , 1751; Walker, 1779; Ward, 1718; Waters, 1721; Watson, 1729; White, 1749; Whitney, 1768; William, 1762; Williston, 1769; Winship, 1772; Witherston, 1798; Wright, 1795.
As to the strangers who are...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Samuel Wakefield | 8 | 4 | 0 | 0 | 0 user votes | |
Wakefield | 150 | 0 | 12 | 0 | 0 user votes | ||
George F. Wakefield | 12 | 0 | 0 | 0 | 0 user votes | ||
William Wakefield | 12 | 0 | 0 | 0 | 0 user votes | ||
W. H. T. Wakefield | 10 | 0 | 0 | 0 | 0 user votes | ||
Gibbon Wakefield | 8 | 0 | 0 | 0 | 0 user votes | ||
L. E. Wakefield | 8 | 0 | 0 | 0 | 0 user votes | ||
Edward Gibbon Wakefield | 6 | 0 | 0 | 0 | 0 user votes | ||
Horace P. Wakefield | 6 | 0 | 0 | 0 | 0 user votes | ||
William H. Wakefield | 6 | 0 | 0 | 0 | 0 user votes | ||
C. H. Wakefield | 4 | 0 | 0 | 0 | 0 user votes | ||
G. W. Wakefield | 4 | 0 | 0 | 0 | 0 user votes | ||
John A. Wakefield | 4 | 0 | 0 | 0 | 0 user votes | ||
Thomas Wakefield | 4 | 2 | 0 | 0 | 0 user votes | ||
George W. Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
Gilbert Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
H. Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
Jerry Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
Priscilla Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
Thomas A. Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
Thomas S. Wakefield | 2 | 0 | 0 | 0 | 0 user votes | ||
A. J. Wakefield | 1 | 0 | 1 | 0 | 0 user votes | ||
Edwin Wakefield | 1 | 0 | 1 | 0 | 0 user votes | ||
John Wakefield | 1 | 0 | 1 | 0 | 0 user votes | ||
Lura Wakefield | 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.