Triple
T28216940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Neville, 16th Earl of Warwick |
E711338
|
entity |
| Predicate | laterSupportedDynasty |
P52346
|
FINISHED |
| Object | House of Lancaster |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: House of Lancaster | Statement: [Richard Neville, 16th Earl of Warwick, laterSupportedDynasty, House of Lancaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSupportedDynasty Context triple: [Richard Neville, 16th Earl of Warwick, laterSupportedDynasty, House of Lancaster]
-
A.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
B.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
C.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
D.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
E.
dynastyServed
chosen
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
- F. None of above.
Provenance (3 batches)
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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 27, 2026, 10:43 p.m.