Triple
T8126776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archibald Primrose, Lord Dalmeny |
E189748
|
entity |
| Predicate | causeOfNotSucceedingToTitle |
P81614
|
FINISHED |
| Object | predeceased his father |
—
|
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: predeceased his father | Statement: [Archibald Primrose, Lord Dalmeny, causeOfNotSucceedingToTitle, predeceased his father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfNotSucceedingToTitle Context triple: [Archibald Primrose, Lord Dalmeny, causeOfNotSucceedingToTitle, predeceased his father]
-
A.
reasonForTitle
Indicates the justification, cause, or basis for assigning a particular title to an entity.
-
B.
titleSucceededFrom
Indicates that a person or entity obtained a title previously held by another, directly following them in succession.
-
C.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
D.
providedTitle
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4c496a8c81909aea840248d85d50 |
completed | March 31, 2026, 4:23 a.m. |
Created at: March 30, 2026, 5:34 p.m.