Triple

T9054755
Position Surface form Disambiguated ID Type / Status
Subject Conquest of Mesopotamia E216969 entity
Predicate instanceOf P0 FINISHED
Object Roman–Parthian war C25533 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–Parthian war
Context triple: [Conquest of Mesopotamia, instanceOf, Roman–Parthian war]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. Byzantine–Bulgarian conflict
    The Byzantine–Bulgarian conflict refers to the series of military, political, and diplomatic struggles between the Byzantine Empire and the medieval Bulgarian states over dominance in the Balkans from the late 7th to the early 15th centuries.
  • 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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
Created at: March 30, 2026, 7:10 p.m.