Triple
T30862386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Aurelius Severus Antoninus |
E786094
|
entity |
| Predicate | reignStartAsCoEmperor |
P50172
|
FINISHED |
| Object | 198 |
—
|
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: 198 | Statement: [Marcus Aurelius Severus Antoninus, reignStartAsCoEmperor, 198]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsCoEmperor Context triple: [Marcus Aurelius Severus Antoninus, reignStartAsCoEmperor, 198]
-
A.
reignAsCoRulerStart
chosen
Indicates the time or event when an entity begins to exercise ruling authority jointly with one or more other rulers.
-
B.
reignAsTitularEmperorStart
Indicates the point in time when an individual begins to hold the title and status of emperor in name, without necessarily exercising actual governing power.
-
C.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
-
D.
reignStartAsKing
Indicates the time or event at which an individual begins their reign in the role of king.
-
E.
successorAsCoRegent
Indicates that one entity becomes the next co-ruling authority alongside an existing ruler, succeeding another in the role of co-regent.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 8:47 p.m.