Triple
T13820879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salome I |
E332130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Herodian dynasty noble |
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: Herodian dynasty noble Context triple: [Salome I, instanceOf, Herodian dynasty noble]
-
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.
Isaurian dynasty ruler
An Isaurian dynasty ruler is a Byzantine emperor from the 8th–9th century Isaurian line who governed the Eastern Roman Empire and is often associated with initiating and enforcing the policy of iconoclasm.
-
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 Theodosian dynasty
A member of the Theodosian dynasty is an individual belonging to the late Roman imperial family founded by Emperor Theodosius I, which ruled parts of the Roman Empire from the late 4th to the mid-5th century CE.
-
E.
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.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:12 p.m.