Triple
T3160064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herodias |
E66080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Herodian dynasty |
C4224
|
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 Herodian dynasty Context triple: [Herodias, instanceOf, member of the Herodian dynasty]
-
A.
Herodian dynasty member
chosen
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 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.
-
C.
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.
-
D.
member of the Hussein family
A member of the Hussein family is an individual who belongs by blood, marriage, or adoption to the familial lineage identified by the Hussein surname and its shared heritage, responsibilities, and relationships.
-
E.
Hasmoneans
The Hasmoneans were a Jewish priestly dynasty that led the Maccabean revolt against Seleucid rule and subsequently governed an independent Judean kingdom in the 2nd–1st centuries BCE.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:05 p.m.