Triple
T30220993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of the Aduatuci stronghold |
E768343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Gallic Wars |
C11928
|
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 Gallic Wars Context triple: [siege of the Aduatuci stronghold, instanceOf, battle of the Gallic Wars]
-
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.
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.
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.
-
D.
Roman military campaign
chosen
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.
-
E.
battle of the Wars of the Diadochi
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.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:35 p.m.