Triple
T3463652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sheffield, 1st Duke of Buckingham and Normanby |
E73083
|
entity |
| Predicate | createdDukeInYear |
P14035
|
FINISHED |
| Object | 1703 |
—
|
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: 1703 | Statement: [John Sheffield, 1st Duke of Buckingham and Normanby, createdDukeInYear, 1703]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdDukeInYear Context triple: [John Sheffield, 1st Duke of Buckingham and Normanby, createdDukeInYear, 1703]
-
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.
createdDukeOfFifeBy
Indicates that one entity conferred or established the title "Duke of Fife" upon another entity.
-
C.
createdEarlBy
Indicates that an entity was granted or established as an earl by a specific creator or authority.
-
D.
royalDesignationYear
chosen
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
E.
createdDukeOfClarence
Indicates the relationship in which one entity formally granted or established the noble title "Duke of Clarence" for another entity.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb0b73f481908c9f8d2b9b9bbbaf |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.