Triple
T30681310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saloninus |
E781057
|
entity |
| Predicate | successorAsRulerInGaul |
P87012
|
FINISHED |
| Object | Postumus |
—
|
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: Postumus | Statement: [Saloninus, successorAsRulerInGaul, Postumus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsRulerInGaul Context triple: [Saloninus, successorAsRulerInGaul, Postumus]
-
A.
successorAsGallicEmperor
chosen
Indicates that one entity became the next Gallic Emperor following another in the line of succession.
-
B.
predecessorAsGallicEmperor
Indicates that one entity served as the immediately preceding Gallic Emperor to the other entity.
-
C.
successorAsKingOfTheFranks
Indicates that one person became the next king of the Franks after another person.
-
D.
successorAsEasternAugustus
Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
-
E.
successorAsKingOfTheRomans
Indicates that one person is the next holder of the title "King of the Romans" following another person in the line of succession.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: April 29, 2026, 8:32 p.m.