Triple
T8924520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Brundisium |
E212506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of Caesar's Civil War |
C21550
|
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 Caesar's Civil War Context triple: [Siege of Brundisium, instanceOf, battle of Caesar's Civil War]
-
A.
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.
-
B.
civil war battle
chosen
A civil war battle is an armed conflict between organized factions within the same country, typically involving large-scale military engagements over political, territorial, or ideological control.
-
C.
battle of the First Punic War
A battle of the First Punic War is a specific military engagement fought between Rome and Carthage (and their allies) between 264 and 241 BCE, characterized by evolving naval and land tactics that shaped the course of Mediterranean power.
-
D.
Byzantine–Sasanian war
The Byzantine–Sasanian war is a prolonged series of military conflicts between the Eastern Roman (Byzantine) Empire and the Sasanian Persian Empire, marked by shifting frontiers, religious and political rivalry, and significant impacts on the balance of power in the Late Antique Near East.
-
E.
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.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.