Triple
T3247967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Frigidus |
E68108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman civil war battle |
C647
|
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: Roman civil war battle Context triple: [Battle of the Frigidus, instanceOf, Roman civil war battle]
-
A.
Roman military campaign
A Roman military campaign is a coordinated series of operations conducted by Roman forces, combining strategic planning, logistics, and battlefield tactics to achieve political, territorial, or defensive objectives.
-
B.
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.
-
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.
battles
chosen
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
-
E.
battle of the Irish Confederate Wars
A battle of the Irish Confederate Wars is a specific military engagement fought in Ireland between 1641 and 1653 involving Irish Confederate, English Royalist, Parliamentarian, or Scottish Covenanter forces as part of the wider Wars of the Three Kingdoms.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:09 p.m.