Triple
T30462673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reign of Macrinus |
E775053
|
entity |
| Predicate | succeededByEmperor |
P197355
|
FINISHED |
| Object | Elagabalus |
—
|
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: Elagabalus | Statement: [Reign of Macrinus, succeededByEmperor, Elagabalus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByEmperor Context triple: [Reign of Macrinus, succeededByEmperor, Elagabalus]
-
A.
successorAsSeniorEmperor
Indicates that one entity becomes the next holder of the position of senior emperor after another entity.
-
B.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
-
C.
successorAsWesternEmperor
Indicates that one individual directly followed another in the role of Western Roman Emperor.
-
D.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
E.
successorAsLatinEmperor
Indicates that one entity became the next holder of the title of Latin Emperor after another entity.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
| PDg | Predicate description generation | batch_69fe8dde8d008190b03dc0f97618073c |
completed | May 9, 2026, 1:29 a.m. |
Created at: April 29, 2026, 8:10 p.m.