Triple
T319501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Fife |
E7780
|
entity |
| Predicate | hasSuccessionType |
P8007
|
FINISHED |
| Object | hereditary succession |
—
|
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: hereditary succession | Statement: [Duke of Fife, hasSuccessionType, hereditary succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessionType Context triple: [Duke of Fife, hasSuccessionType, hereditary succession]
-
A.
successionDefinedBy
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
-
B.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
C.
successionPattern
chosen
Indicates the characteristic way in which one entity follows, replaces, or is ordered after another in a sequence or succession.
-
D.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
E.
successorClass
Indicates that one class directly follows or replaces another class in a sequence or hierarchy.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e94513ec819089f5177f7a521e65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.