Statistics for occurrence #1 of “Westminster” in chapter 17, page 376 of Horace Greeley, The American Conflict: A History of the Great Rebellion in the United States of America, 1860-65: its Causes, Incidents, and Results: Intended to exhibit especially its moral and political phases with the drift and progress of American opinion respecting human slavery from 1776 to the close of the War for the Union. Volume II.:
...t, with a considerable proportion of the Rebel cavalry, was watching on our left flank when Hooker crossed the Potomac, and crossed himself at Seneca soon afterward; moving up on our right so far as Westminster ; burning 17 canal boats, also a train of 178 army wagons, laden with army stores, and picking up quite a number of our officers who were hastening to join their regiments at the front.
From Westmin...
Max. Freq. | Min. Freq. | ||||||
---|---|---|---|---|---|---|---|
Entity | Corpus | Doc | Corpus | Doc | |||
† | Westminster (Maryland, United States) | 536 | 4 | 18 | 0 | 0 user votes | |
Westminster (Massachusetts, United States) | 119 | 0 | 5 | 0 | 0 user votes | ||
Westminster (United Kingdom) | 65 | 0 | 1 | 0 | 0 user votes | ||
Westminster (United Kingdom) | 4 | 0 | 4 | 0 | 0 user votes | ||
Westminster (California, United States) | 2 | 0 | 0 | 0 | 0 user votes | ||
Westminster (South Carolina, United States) | 1 | 0 | 1 | 0 | 0 user votes | ||
Westminster (Vermont, United States) | 1 | 0 | 1 | 0 | 0 user votes | ||
Westminster (Colorado, United States) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (Delaware, United States) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (Louisiana, United States) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (Ohio, United States) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (Pennsylvania, United States) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (Texas, United States) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (United Kingdom) | 0 | 0 | 0 | 0 | 0 user votes | ||
Westminster (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.