Triple
T31104685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Corrino |
E792761
|
entity |
| Predicate | successionDisruptedBy |
P32191
|
FINISHED |
| Object | Paul Atreides |
—
|
NE NERFINISHED |
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: Paul Atreides | Statement: [House Corrino, successionDisruptedBy, Paul Atreides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionDisruptedBy Context triple: [House Corrino, successionDisruptedBy, Paul Atreides]
-
A.
successionConflict
chosen
Indicates a dispute or struggle over who has the legitimate right to succeed to a position, title, or authority.
-
B.
successionIssue
Indicates a relationship where there is a dispute, complication, or question regarding who is entitled to succeed or inherit a position, title, or estate.
-
C.
successionOutcome
Indicates the result or consequence of a succession event, such as who or what ultimately assumes a position, role, or status after a predecessor.
-
D.
successionTrigger
Indicates a condition or event that initiates or causes a transfer of position, role, or authority from one entity to another.
-
E.
successionAction
Indicates an action or event through which one entity formally replaces or follows another in a sequence or position.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 29, 2026, 9:03 p.m.