Triple
T30465474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Raudine Plain |
E775125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman 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 battle Context triple: [Battle of the Raudine Plain, instanceOf, Roman 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.
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.
-
C.
Roman–Sasanian War engagement
A Roman–Sasanian War engagement is a specific military confrontation between Roman (or Eastern Roman/Byzantine) and Sasanian Persian forces within the broader series of Roman–Sasanian conflicts.
-
D.
battle of the Roman–Palmyrene War
A battle of the Roman–Palmyrene War is a military engagement between Roman imperial forces and the Palmyrene Empire, fought during the 3rd century crisis to determine regional control in the Eastern Mediterranean and Near East.
-
E.
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.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:11 p.m.