Triple
T15320946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward of Norwich, 2nd Duke of York |
E366287
|
entity |
| Predicate | succeededAsDukeOfYorkIn |
P47423
|
FINISHED |
| Object | 1402 |
—
|
LITERAL FINISHED |
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: 1402 | Statement: [Edward of Norwich, 2nd Duke of York, succeededAsDukeOfYorkIn, 1402]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAsDukeOfYorkIn Context triple: [Edward of Norwich, 2nd Duke of York, succeededAsDukeOfYorkIn, 1402]
-
A.
successorAsDukeOfYork
Indicates that one person became the next holder of the title Duke of York after another person.
-
B.
reignAsDukeOfYorkEnd
Indicates the point in time or event at which an individual’s tenure or rule as Duke of York comes to an end.
-
C.
successorAsDukeOfKentAndStrathearn
Indicates that one entity became the next holder of the title "Duke of Kent and Strathearn" after another entity.
-
D.
reignAsDukeOfYorkStart
chosen
Indicates the time at which an individual begins their tenure holding the title and authority of Duke of York.
-
E.
succeededByAsKingOfHanover
Indicates that one individual was directly followed by another as the reigning king of Hanover.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd460288190b5c41f0a0aeee949 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.