Triple
T16286502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James FitzGerald, 1st Duke of Leinster |
E395400
|
entity |
| Predicate | createdMarquessOfKildare |
P55713
|
FINISHED |
| Object | 1761 |
—
|
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: 1761 | Statement: [James FitzGerald, 1st Duke of Leinster, createdMarquessOfKildare, 1761]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdMarquessOfKildare Context triple: [James FitzGerald, 1st Duke of Leinster, createdMarquessOfKildare, 1761]
-
A.
createdMarquess
chosen
Indicates that one entity formally established or granted the noble title of marquess to another entity.
-
B.
createdDukeOfFifeBy
Indicates that one entity conferred or established the title "Duke of Fife" upon another entity.
-
C.
createdDukeOfLennoxBy
Indicates the person or authority that formally established or conferred the title of Duke of Lennox upon someone.
-
D.
createdDukeOfClarence
Indicates the relationship in which one entity formally granted or established the noble title "Duke of Clarence" for another entity.
-
E.
createdDukeOfYorkBy
Indicates the action by which an authority or agent formally conferred or established the title of Duke of York upon a person.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.