Triple
T19921016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wars of the Diadochi |
E478794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic conflict |
C37598
|
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: Hellenistic conflict Context triple: [Wars of the Diadochi, instanceOf, Hellenistic conflict]
-
A.
Hellenistic-period conflict
chosen
A Hellenistic-period conflict is a military or political struggle occurring between Alexander the Great’s death in 323 BCE and the Roman conquest of the eastern Mediterranean, typically involving successor kingdoms vying for territory, power, and influence.
-
B.
Greek–Persian conflict
The Greek–Persian conflict is a historical class representing the prolonged series of political, military, and cultural confrontations between the Greek city-states and the Persian Empire, encompassing causes, key battles, strategies, and outcomes that shaped classical antiquity.
-
C.
Diadochi
The Diadochi were the rival generals, companions, and successors of Alexander the Great who fought to control and divide his vast empire after his death.
-
D.
Roman–Pontic war
The Roman–Pontic war was a series of military conflicts between the Roman Republic and the Kingdom of Pontus, primarily under King Mithridates VI, over control of Asia Minor and the eastern Mediterranean in the 1st century BCE.
-
E.
battle of the Wars of the Diadochi
A battle of the Wars of the Diadochi is a military engagement fought between rival successors of Alexander the Great as they contested control over fragments of his former empire.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:53 p.m.