Home / Topics / Neville Name Inventory in Shakespeare

Neville Name Inventory in Shakespeare

Mixed Needs Review source map packet

Topic: Neville Name Inventory in Shakespeare

Source-Control Verdict

This topic file was missing from NEVILLE_AI_TOPICS/topics/ when the Worker E batch began. The current canonical AI topic appears to be neville name references in shakespeare canon, which was outside this worker's edit scope. This packet records the inventory control needed by the genealogy batch without editing that canonical file.

The direct surname result is narrow. A Folger chunk search for:

rg -n -i "\bNevil|\bNevill|\bNeville|\bNevilles" [local source path removed]

found direct Nevil surname hits only in 2 Henry VI and 2 Henry IV*. The complete Folger XML audit reported below now replaces this preliminary chunk-search control.

Quoted Source Passages

Folger local chunk, 2 Henry VI 1.3, lines 117-120:

SUFFOLK

And he of these that can do most of all

Cannot do more in England than the Nevilles;

Salisbury and Warwick are no simple peers.

Source: act 01 scene 03:117.

Folger local chunk, 2 Henry VI 2.2, lines 20-24:

WARWICK

Sweet York, begin; and if thy claim be good,

The Nevilles are thy subjects to command.

YORK Then thus:

Source: act 02 scene 02:20.

Folger local chunk, 2 Henry IV 3.1, lines 90-95:

And laid his love and life under my foot,

Yea, for my sake, even to the eyes of Richard

Gave him defiance. But which of you was by--

[To Warwick.] You, cousin Nevil, as I may

remember--

When Richard, with his eye brimful of tears,

Source: act 03 scene 01:90. Line breaks, speech context, and stage direction follow the Folger witness.

Direct Surname Hits

2 Henry VI

2 Henry IV

Title / Person References

The batch also checked title/person terms in the Folger chunks. Westmoreland, Westmorland, Warwick, Salisbury, and Abergavenny occur as title or person references, not as direct Neville surname hits. They should be routed to child packets and genealogy tables rather than counted as direct Neville-name occurrences.

The strongest controlled examples for this family-network batch are:

BRO Genealogy Controls

BRO evidence helps with titleholder and family-identity control, not with the Shakespeare text inventory itself:

Demoted Claims

2026-07-14 Complete Folger XML Inventory

The complete Folger XML corpus was searched at word-token level for every token beginning Nevil, including the one-l spelling Nevil. The result is eight tokens in two plays:

PlayXML anchorFolger token
2 Henry VI1.1.251Nevilles’
2 Henry VI1.3.75Nevilles
2 Henry VI2.2.8Nevilles
2 Henry VI2.2.85Neville
2 Henry VI3.2.223Nevilles’
2 Henry VI4.1.97Nevilles
2 Henry VI5.1.206Neville’s
2 Henry IV3.1.66Nevil

The most explicit family-language in 2 Henry VI includes:

And he of these that can do most of all

Cannot do more in England than the Nevilles;

Salisbury and Warwick are no simple peers.

—2 Henry VI 1.3.74-76, Folger.

The play also makes ancestry, legitimacy, and a distinctive badge dramatically explicit:

Now, by my father's badge, old Neville's crest,

The rampant bear chained to the ragged staff,

This day I'll wear aloft my burgonet—

—2 Henry VI 5.1.206-208, Folger.

The 2 Henry IV token is an address to Warwick:

But which of you was by—

You, cousin Nevil, as I may remember—

When Richard, with his eye brimful of tears,

—2 Henry IV 3.1.65-67, Folger.

What the inventory changes

The direct surname is concentrated, not dispersed. 2 Henry VI repeatedly speaks of the Nevilles, their noble race, their collective force, and their badge. 2 Henry IV supplies the sole direct form elsewhere in the Folger XML corpus. Warwick, Salisbury, Westmorland/Westmoreland, and Abergavenny remain essential to a Neville-family study, but they are title/person references and should be counted in a separate layer.

The concentration is a factual map for future source and genealogy work. It does not by itself identify a modern Neville, establish autobiographical reference, or decide authorship.

Reproducibility

Corpus: [local source path removed]. Every ZIP was parsed, every TEI w element was inspected, and matching required the normalized word text to begin nevil. This corrected the risk that a plain-text query might omit the one-l Nevil form.

Citations

Notes on Access