Statistics for occurrence #1 of “Battle” in chapter 15 of Rebellion Record: a Diary of American Events: Documents and Narratives, Volume 4.:

...he alleged, that the enemy should make an attack on our breastworks. Gen. Crittenden, however, insisting that his plan should be carried into execution, Gen. Zollicoffer, at the head of portions of Battle 's, Newman's, Stanton's, Powell's, and Murray's Tennessee regiments, and the Fifteenth Mississippi regiment, under Col. Stratham, together with an Alabama regiment, (the Fourteenth, we believe,) proce...
Max. Freq. Min. Freq.
Entity Corpus Doc Corpus Doc  
William Battle 42 38 0 0 0 user votes
C. A. Battle 233 0 19 0 0 user votes
Battle 149 0 39 0 0 user votes
Cullen A. Battle 122 0 6 0 0 user votes
Cullen Andrews Battle 33 0 9 0 0 user votes
J. A. Battle 19 0 1 0 0 user votes
James S. Battle 14 0 0 0 0 user votes
J. S. Battle 12 0 2 0 0 user votes
Joel A. Battle 10 0 4 0 0 user votes
Kemp P. Battle 10 0 0 0 0 user votes
N. W. Battle 7 0 3 0 0 user votes
Q. M. Battle 6 0 0 0 0 user votes
H. T. Battle 5 0 1 0 0 user votes
Jennie L. Battle 5 0 1 0 0 user votes
L. W. Battle 5 0 3 0 0 user votes
Junius C. Battle 4 0 0 0 0 user votes
W. H. Battle 4 0 0 0 0 user votes
Wesley Lewis Battle 4 0 2 0 0 user votes
William S. Battle 4 0 0 0 0 user votes
Dorsey Battle 3 0 1 0 0 user votes
Fannie Battle 3 0 1 0 0 user votes
John Battle 3 1 3 1 0 user votes
A. Q. M. Battle 2 0 0 0 0 user votes
Frank Battle 2 0 2 0 0 user votes
J. Battle 2 0 0 0 0 user votes
J. B. Battle 2 0 0 0 0 user votes
K. P. Battle 2 0 0 0 0 user votes
Kemp Plummer Battle 2 0 0 0 0 user votes
R. H. Battle 2 0 0 0 0 user votes
Thomas Battle 2 0 2 0 0 user votes
C. C. Battle 1 0 1 0 0 user votes
Cullen Battle 1 0 1 0 0 user votes
G. W. Battle 1 0 1 0 0 user votes
H. J. G. Battle 1 0 1 0 0 user votes
Henry W. Battle 1 0 1 0 0 user votes
J. W. Battle 1 0 1 0 0 user votes
Kemp Battle 1 0 1 0 0 user votes
Kemp B. Battle 1 0 1 0 0 user votes
Samuel G. Battle 1 0 1 0 0 user votes
William J. Battle 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.