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

...ove McClernand to Fourteen-mile creek, early to-morrow, so that he will occupy a place on Sherman's left. . . . Accordingly, on the 12th, at three and a half A. M., Logan's division moved towards Raymond , followed by Crocker, at four. The rebel videttes showed themselves frequently soon after the march began, and three miles out, McPherson ordered two regiments to be deployed on each side of the ro...
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.