Triple
T32778111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Sentinum |
E838274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman-Samnite war battle |
C57036
|
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-Samnite war battle Context triple: [Battle of Sentinum, instanceOf, Roman-Samnite war battle]
-
A.
Roman–Dacian war
The Roman–Dacian war refers to the series of military conflicts between the Roman Empire and the Dacian Kingdom in the late 1st and early 2nd centuries AD, culminating in Rome’s conquest and annexation of Dacia under Emperor Trajan.
-
B.
Roman–Parthian war
The Roman–Parthian war is a conceptual class representing the series of military conflicts and political struggles between the Roman Empire and the Parthian Empire over control of territories in the Near East from the 1st century BCE to the 3rd century CE.
-
C.
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.
-
D.
Roman battle
chosen
A Roman battle is a large-scale military engagement in which Roman forces, often organized into legions and auxiliaries, confront enemy armies using disciplined formations, tactical maneuvers, and a combination of infantry, cavalry, and siege weaponry.
-
E.
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.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:13 a.m.