Statistics for occurrence #1 of “Lowell” in page 263 of William Schouler, A history of Massachusetts in the Civil War: Volume 1:
...e place.
It does not appear that the letter of the Governor of Oct. 5 changed in the least degree the determination of General Butler to enlist men. He opened a camp in Pittsfield, and another in Lowell , and commenced recruiting two regiments of infantry,
...
|
Max. Freq. |
Min. Freq. |
|
|
Entity |
Corpus |
Doc |
Corpus |
Doc |
|
| † |
Lowell (Massachusetts, United States) |
933 |
40 |
91 |
0 |
0 user votes |
|
Lowell (California, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Florida, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Georgia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Idaho, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Indiana, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Iowa, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Kansas, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Kentucky, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Maine, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Michigan, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Missouri, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Missouri, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Nebraska, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (New York, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (North Carolina, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (North Dakota, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Oregon, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Pennsylvania, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Vermont, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (West Virginia, United States) |
0 |
0 |
0 |
0 |
0 user votes |
|
Lowell (Wisconsin, 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.