Triple
T16286503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James FitzGerald, 1st Duke of Leinster |
E395400
|
entity |
| Predicate | succeededAsEarlOfKildare |
P122535
|
FINISHED |
| Object | 1744 |
—
|
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: 1744 | Statement: [James FitzGerald, 1st Duke of Leinster, succeededAsEarlOfKildare, 1744]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAsEarlOfKildare Context triple: [James FitzGerald, 1st Duke of Leinster, succeededAsEarlOfKildare, 1744]
-
A.
successorAsEarlOfMorton
Indicates the person who became the next Earl of Morton after the previous holder of the title.
-
B.
successorAsEarlOfBothwell
Indicates the person who became the next Earl of Bothwell after the previous holder of that title.
-
C.
successorAsEarlOfHuntingdon
Indicates that one person became the next Earl of Huntingdon following another person in that title or office.
-
D.
successorAsKingOfIreland
Indicates that one entity became the next king of Ireland following another entity.
-
E.
successorAsEarlOfNorthumbria
Indicates that one entity became the next Earl of Northumbria following another entity in succession.
- 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_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. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.