Triple
T19491570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lysimachia |
E487663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hellenistic-era battle |
C36073
|
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-era battle Context triple: [Battle of Lysimachia, instanceOf, Hellenistic-era battle]
-
A.
Hellenistic-period conflict
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.
Bronze Age battle
A Bronze Age battle is an armed conflict between organized groups during the Bronze Age, typically involving bronze weapons, chariots, early fortifications, and tactics shaped by emerging complex societies.
-
C.
battle of the Wars of the Diadochi
chosen
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.
-
D.
1st-century BCE conflict
A 1st-century BCE conflict is a historically documented military or political struggle that occurred between 100 BCE and 1 BCE, involving organized groups or states engaged in warfare or sustained hostilities.
-
E.
ancient Greek war
Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.