Triple
T2333314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domitian |
E44252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Flavian dynasty |
C10074
|
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: member of the Flavian dynasty Context triple: [Domitian, instanceOf, member of the Flavian dynasty]
-
A.
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.
-
B.
member of the Constantinian dynasty
A member of the Constantinian dynasty is an individual belonging to the imperial family that ruled the Roman Empire from the rise of Constantine the Great in the early 4th century until the death of his descendants later that century.
-
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 gens Claudia
A member of the gens Claudia is an individual belonging to the ancient Roman patrician (and later plebeian) family Claudia, known for its prominent political, military, and social influence in the Roman Republic and Empire.
-
E.
Roman empress
A Roman empress is the wife or female counterpart of a Roman emperor, often wielding significant political, social, and cultural influence within the imperial court and broader empire.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:51 p.m.