Triple

T2376733
Position Surface form Disambiguated ID Type / Status
Subject Roman–Parthian War of 161–166 E46214 entity
Predicate instanceOf P0 FINISHED
Object Roman–Parthian War C2457 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: [Roman–Parthian War of 161–166, instanceOf, Roman–Parthian 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. Mongol invasion of the Middle East
    The Mongol invasion of the Middle East was a series of 13th- and 14th-century military campaigns by the Mongol Empire that devastated major Islamic centers, reshaped regional political structures, and facilitated new patterns of trade and cultural exchange across Eurasia.
  • C. imperial war chosen
    Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
  • D. ancient Greek war
    Ancient Greek war encompasses the organized, often city-state-driven conflicts of classical Greece, characterized by hoplite phalanxes, naval battles like those at Salamis, shifting alliances, and a fusion of military, political, and cultural motives.
  • E. battle of the Second Anglo-Dutch War
    A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict for maritime and commercial supremacy.
  • 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_69a88a1554a48190a0180682bcf099be completed March 4, 2026, 7:37 p.m.
Created at: March 4, 2026, 7:57 p.m.