Triple
T8411757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mylae |
E198640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the First Punic War |
C24293
|
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: battle of the First Punic War Context triple: [Battle of Mylae, instanceOf, battle of the First Punic War]
-
A.
Punic War
The Punic War is a historical conflict between ancient Rome and Carthage, characterized by a series of three wars fought from 264 to 146 BCE for dominance over the western Mediterranean.
-
B.
battle of the Italian Wars
A battle of the Italian Wars is a military engagement fought between 1494 and 1559 among major European powers over control of the Italian peninsula, typically involving shifting alliances, evolving tactics, and significant political consequences.
-
C.
battle of the Nine Years' War
A battle of the Nine Years' War is a military engagement fought between 1688 and 1697 involving the Grand Alliance and France, characterized by early modern tactics, shifting coalitions, and the broader struggle for European balance of power.
-
D.
Byzantine–Vandal War
The Byzantine–Vandal War (533–534) was a military campaign in which the Eastern Roman (Byzantine) Empire under Emperor Justinian I defeated the Vandal Kingdom in North Africa, restoring imperial control over the region.
-
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. 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:05 p.m.