Statistics for occurrence #1 of “Raymond” in chapter 8, page 267 of Adam Badeau, Military history of Ulysses S. Grant from April 1861 to April 1865. Volume 1:

...roken and fled from the field. Logan's attack had precipitated the rout, and the battle of Champion's hill was won. This was between three and four o'clock in the afternoon. Arriving now at the Raymond road, Grant saw on his left, and along the next ridge, a column of troops approaching, which proved to be Carr's division: Mc-Clernand was with it in person. To the left of Carr, Osterhaus soon aft...
Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
Raymond (Mississippi, United States) 764 97 26 1 0 user votes
Raymond (New Hampshire, United States) 3 0 3 0 0 user votes
Raymond (Arkansas, United States) 0 0 0 0 0 user votes
Raymond (California, United States) 0 0 0 0 0 user votes
Raymond (Canada) 0 0 0 0 0 user votes
Raymond (Colorado, United States) 0 0 0 0 0 user votes
Raymond (Georgia, United States) 0 0 0 0 0 user votes
Raymond (Idaho, United States) 0 0 0 0 0 user votes
Raymond (Illinois, United States) 0 0 0 0 0 user votes
Raymond (Indiana, United States) 0 0 0 0 0 user votes
Raymond (Iowa, United States) 0 0 0 0 0 user votes
Raymond (Kansas, United States) 0 0 0 0 0 user votes
Raymond (Kentucky, United States) 0 0 0 0 0 user votes
Raymond (Louisiana, United States) 0 0 0 0 0 user votes
Raymond (Maine, United States) 0 0 0 0 0 user votes
Raymond (Massachusetts, United States) 0 0 0 0 0 user votes
Raymond (Minnesota, United States) 0 0 0 0 0 user votes
Raymond (Missouri, United States) 0 0 0 0 0 user votes
Raymond (Montana, United States) 0 0 0 0 0 user votes
Raymond (New York, United States) 0 0 0 0 0 user votes
Raymond (Pennsylvania, United States) 0 0 0 0 0 user votes
Raymond (South Dakota, United States) 0 0 0 0 0 user votes
Raymond (Texas, United States) 0 0 0 0 0 user votes
Raymond (Utah, United States) 0 0 0 0 0 user votes
Raymond (Washington, United States) 0 0 0 0 0 user votes
Raymond (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.