Triple
T22993338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antipater I |
E572115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Antipatrid dynasty |
C47109
|
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 Antipatrid dynasty Context triple: [Antipater I, instanceOf, member of the Antipatrid dynasty]
-
A.
member of the Antigonid dynasty
A member of the Antigonid dynasty is an individual belonging to the Hellenistic royal family that ruled Macedonia and parts of Greece from the late 4th to the 2nd century BCE, descending from Antigonus I Monophthalmus.
-
B.
member of the Argead dynasty
A member of the Argead dynasty is an individual belonging to the ancient Macedonian royal house that ruled Macedon, including figures such as Philip II and Alexander the Great.
-
C.
Spartocid dynasty member
A Spartocid dynasty member is an individual belonging to the ruling family of the Bosporan Kingdom, which governed the Cimmerian Bosporus region from the 5th to the 2nd century BCE.
-
D.
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.
-
E.
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.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:50 p.m.