Triple
T14220833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartocus I |
E352485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spartocid dynasty member |
C33598
|
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: Spartocid dynasty member Context triple: [Spartocus I, instanceOf, Spartocid dynasty member]
-
A.
member of the Deinomenid dynasty
A member of the Deinomenid dynasty is an individual belonging to the ruling family that controlled Syracuse and parts of Sicily in the early 5th century BCE, originating from the tyrant Gelon and his relatives.
-
B.
member of the Magonid dynasty
A member of the Magonid dynasty is an individual belonging to the powerful Carthaginian ruling family, active mainly in the 6th–4th centuries BCE, known for producing influential military and political leaders who shaped Carthage’s expansion and foreign policy.
-
C.
member of the Battiad dynasty
A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
-
D.
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.
-
E.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:06 a.m.