Statistics for occurrence #1 of “Ludlow” in chapter 16 of William Schouler, A history of Massachusetts in the Civil War: Volume 2:
... 202
Lee 81
Leicester 639
Leominster 642
Lenox 84
Leverett 271
Lexington 414
Leyden 272
Littleton 419
Lincoln 416
Longmeadow 307
Lowell 420
Ludlow 308
Lunenburg 644
Lynn 207
Lynnfield 212
Malden 425
Manchester 213
Mansfield 139
Marblehead 215
Marlborough 427
Marshfield 557
Marion 557
M...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Ludlow | 107 | 6 | 49 | 0 | 0 user votes | |
William H. Ludlow | 67 | 0 | 9 | 0 | 0 user votes | ||
W. H. Ludlow | 35 | 0 | 9 | 0 | 0 user votes | ||
William Ludlow | 28 | 0 | 8 | 0 | 0 user votes | ||
Roger Ludlow | 22 | 0 | 0 | 0 | 0 user votes | ||
James Ludlow | 10 | 0 | 0 | 0 | 0 user votes | ||
Col W. H. Ludlow | 9 | 0 | 1 | 0 | 0 user votes | ||
John R. Ludlow | 8 | 0 | 2 | 0 | 0 user votes | ||
Nicholl Ludlow | 8 | 0 | 0 | 0 | 0 user votes | ||
Augustus Ludlow | 7 | 0 | 1 | 0 | 0 user votes | ||
Arnold Ludlow | 4 | 0 | 0 | 0 | 0 user votes | ||
Benjamin Chambers Ludlow | 4 | 0 | 0 | 0 | 0 user votes | ||
Nicol Ludlow | 4 | 0 | 0 | 0 | 0 user votes | ||
Edwin Ludlow | 3 | 0 | 1 | 0 | 0 user votes | ||
Mary Ludlow | 3 | 0 | 1 | 0 | 0 user votes | ||
A. S. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
B. C. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
Benjamin C. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
C. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
E. H. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
Gabriel Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
George C. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
J. M. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
John Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
Nicoll Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
Robert Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
Va Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
Wm H. Ludlow | 2 | 0 | 0 | 0 | 0 user votes | ||
George Ludlow | 1 | 0 | 1 | 0 | 0 user votes | ||
W. E. Ludlow | 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.