Triple
T30247644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barracks emperors |
E769101
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of Roman emperors |
C57178
|
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: group of Roman emperors Context triple: [Barracks emperors, instanceOf, group of Roman emperors]
-
A.
Roman imperial dynasty
A Roman imperial dynasty is a succession of emperors from the same family or household who ruled the Roman Empire over a continuous period, sharing political power, legitimacy, and often common policies or agendas.
-
B.
person of the early Roman Empire
A person of the early Roman Empire is an individual living under Roman rule during the first centuries BCE–CE, shaped by Roman law, social hierarchy, imperial politics, and a cosmopolitan Mediterranean culture.
-
C.
member of the Severan dynasty
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.
-
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.
Roman dynasty
A Roman dynasty is a succession of rulers from the same family or lineage who governed the Roman state over a continuous period, shaping its political, social, and cultural development.
- F. None of above. chosen
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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:39 p.m.