Triple
T11844084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothic War (376–382) |
E281726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman military conflict |
C10888
|
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: late Roman military conflict Context triple: [Gothic War (376–382), instanceOf, late Roman military conflict]
-
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.
4th-century conflict
chosen
A 4th-century conflict is a historical dispute, war, or series of hostilities that occurred between 300 and 399 CE, shaped by the political, religious, and social dynamics of late antiquity.
-
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 frontier
The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
-
E.
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.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.