Triple
T10658285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elagabalus |
E251153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Severan dynasty emperor |
C25532
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Severan dynasty emperor Context triple: [Elagabalus, instanceOf, Severan dynasty emperor]
-
A.
3rd-century Roman emperor
A 3rd-century Roman emperor is the sovereign ruler of the Roman Empire during the 200s CE, navigating intense military, political, and economic crises while asserting imperial authority over a vast and often unstable realm.
-
B.
member of the Severan dynasty
chosen
A member of the Severan dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 193 to 235 CE, beginning with Septimius Severus and including his successors such as Caracalla, Elagabalus, and Severus Alexander.
-
C.
4th-century Roman emperor
A 4th-century Roman emperor is a sovereign ruler of the Roman Empire during the 300s CE, navigating military, religious, and administrative transformations that reshaped the ancient Mediterranean world.
-
D.
member of the Flavian dynasty
A member of the Flavian dynasty is an individual belonging to the Roman imperial family that ruled the Roman Empire from 69 to 96 CE, including emperors Vespasian, Titus, and Domitian and their close relatives.
-
E.
Herodian dynasty member
A Herodian dynasty member is an individual belonging to the ruling family established by Herod the Great, which governed Judea and surrounding regions under Roman authority during the late first century BCE and early first century CE.
- F. None of above.
Provenance (1 batch)
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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:07 p.m.