Triple
T7083884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torquhil Campbell, 13th Duke of Argyll |
E165024
|
entity |
| Predicate | succeededAsDuke |
P74880
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Torquhil Campbell, 13th Duke of Argyll, succeededAsDuke, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededAsDuke Context triple: [Torquhil Campbell, 13th Duke of Argyll, succeededAsDuke, 2001]
-
A.
establishedAsDukes
Indicates that certain individuals or entities were formally created or recognized with the rank and title of dukes.
-
B.
successorAsDukeOfBrittany
Indicates that one entity became the next Duke of Brittany following another entity in the line of succession.
-
C.
successorAsDukeOfSavoy
Indicates that one entity became the next Duke of Savoy following another entity in the line of succession.
-
D.
successorAsDukeOfOrléans
Indicates that one entity became the next holder of the title Duke of Orléans after another entity.
-
E.
successorAsDukeOfNormandy
Indicates that one person becomes the next holder of the title Duke of Normandy after another person.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5102be08190bbde790bfa8fe9e2 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:40 p.m.