Triple
T7537041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard of Shrewsbury, Duke of York |
E178176
|
entity |
| Predicate | createdDukeOfYork |
P77685
|
FINISHED |
| Object | 1474-05-28 |
—
|
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: 1474-05-28 | Statement: [Richard of Shrewsbury, Duke of York, createdDukeOfYork, 1474-05-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdDukeOfYork Context triple: [Richard of Shrewsbury, Duke of York, createdDukeOfYork, 1474-05-28]
-
A.
createdDukeOfYorkBy
Indicates the action by which an authority or agent formally conferred or established the title of Duke of York upon a person.
-
B.
createdDukeOfClarence
Indicates the relationship in which one entity formally granted or established the noble title "Duke of Clarence" for another entity.
-
C.
createdDukeOfExeter
Indicates that one entity granted or established the noble title "Duke of Exeter" for another entity.
-
D.
createdDukeOfFifeBy
Indicates that one entity conferred or established the title "Duke of Fife" upon another entity.
-
E.
createdDukeOfElchingen
Indicates the act of conferring the noble title "Duke of Elchingen" upon a person, thereby creating or establishing that dukedom for them.
- F. None of above. chosen
Provenance (4 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84db0c48190b2b3d8c5f802f713 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5cea2748190afd607ef93e8d66c |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:48 p.m.