Triple
T22902920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Neville, Earl of Kent |
E568371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yorkist supporter |
C43867
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Yorkist supporter Context triple: [William Neville, Earl of Kent, instanceOf, Yorkist supporter]
-
A.
Lancastrian supporter
A Lancastrian supporter is an individual who backed the House of Lancaster’s claim to the English throne during the Wars of the Roses, often opposing the rival House of York.
-
B.
supporter of the House of York
chosen
A supporter of the House of York is an individual who aligns with and advocates for the political, dynastic, or symbolic interests of the Yorkist branch of the English royal family, particularly during the Wars of the Roses.
-
C.
supporter of Henry VII of England
A supporter of Henry VII of England is an individual who backed Henry Tudor’s claim to the English throne and aided his rise and consolidation of power, particularly during and after the Wars of the Roses.
-
D.
supporter of Henry III of England
A supporter of Henry III of England is an individual, whether noble, cleric, or commoner, who remained loyal to and actively backed the king’s authority, policies, and dynastic interests during his reign from 1216 to 1272.
-
E.
supporter of William the Conqueror
A supporter of William the Conqueror is an individual, group, or institution that actively aided, endorsed, or benefited from William’s claim to and consolidation of the English throne before, during, or after the Norman Conquest of 1066.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:41 p.m.