Triple
T17293267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antigonus III Doson |
E419840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Antigonid dynasty |
C39032
|
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 Antigonid dynasty Context triple: [Antigonus III Doson, instanceOf, member of the Antigonid dynasty]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
member of the Heraclian dynasty
A member of the Heraclian dynasty is an individual belonging to the Byzantine imperial family that ruled from Emperor Heraclius’s accession in 610 to the death of Justinian II in 711, linked by blood or marriage to this ruling house.
-
E.
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.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.