Triple
T14159686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domitian's Dacian Wars |
E350903
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman–Dacian war |
C33520
|
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–Dacian war Context triple: [Domitian's Dacian Wars, instanceOf, Roman–Dacian war]
-
A.
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.
-
B.
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.
-
C.
Illyrian revolt
The Illyrian revolt was a significant uprising by the Illyrian tribes against Roman rule in the early 1st century CE, challenging Roman authority in the western Balkans.
-
D.
Byzantine–Vandal War
The Byzantine–Vandal War (533–534) was a military campaign in which the Eastern Roman (Byzantine) Empire under Emperor Justinian I defeated the Vandal Kingdom in North Africa, restoring imperial control over the region.
-
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. 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 12:58 a.m.