Triple
T8345660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antigonus I Monophthalmus |
E196027
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diadochi ruler |
C15338
|
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: Diadochi ruler Context triple: [Antigonus I Monophthalmus, instanceOf, Diadochi ruler]
-
A.
Seleucid king
A Seleucid king is a Hellenistic monarch who ruled parts of the former Alexandrian empire in the Near East under the Seleucid dynasty, exercising military, administrative, and cultural authority over a diverse, multiethnic realm.
-
B.
Hellenistic-era monarch
chosen
A Hellenistic-era monarch is a ruler who governed one of the successor kingdoms to Alexander the Great’s empire, blending Greek political and cultural traditions with local customs across a diverse, often expansive territory.
-
C.
regent of the Seleucid Empire
A regent of the Seleucid Empire is an individual who temporarily governed the Hellenistic Seleucid state on behalf of an underage, absent, or otherwise incapacitated king, exercising royal authority without holding the full royal title.
-
D.
Macedonian king
A Macedonian king is a sovereign ruler of the ancient kingdom of Macedonia, wielding military, political, and religious authority over its territories and people.
-
E.
Seleucid general
A Seleucid general is a high-ranking military commander serving the Hellenistic Seleucid Empire, responsible for leading armies, managing campaigns, and maintaining imperial control over diverse and often contested territories.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:58 p.m.