Triple
T2113261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Segusio |
E42550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Roman civil wars |
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: battle of the Roman civil wars Context triple: [Siege of Segusio, instanceOf, battle of the Roman civil wars]
-
A.
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.
-
B.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
C.
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.
-
D.
succession war
A succession war is an armed conflict triggered by competing claims to a throne or leadership position, typically following the death, deposition, or disputed legitimacy of a ruler.
-
E.
battle of the Franco-Dutch War
A battle of the Franco-Dutch War is a military engagement fought between 1672 and 1678 involving France and its allies against the Dutch Republic and its shifting coalition of European powers, typically characterized by complex political motives and evolving alliances.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:43 p.m.