Triple

T15182657
Position Surface form Disambiguated ID Type / Status
Subject Battle of Salamis in Cyprus (306 BC) E362782 entity
Predicate instanceOf P0 FINISHED
Object Hellenistic military conflict C23996 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: Hellenistic military conflict
Context triple: [Battle of Salamis in Cyprus (306 BC), instanceOf, Hellenistic military conflict]
  • A. Greek–Persian conflict
    The Greek–Persian conflict is a historical class representing the prolonged series of political, military, and cultural confrontations between the Greek city-states and the Persian Empire, encompassing causes, key battles, strategies, and outcomes that shaped classical antiquity.
  • B. Diadochi chosen
    The Diadochi were the rival generals, companions, and successors of Alexander the Great who fought to control and divide his vast empire after his death.
  • C. 1st-century BCE conflict
    A 1st-century BCE conflict is a historically documented military or political struggle that occurred between 100 BCE and 1 BCE, involving organized groups or states engaged in warfare or sustained hostilities.
  • D. 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.
  • E. 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.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
Created at: April 10, 2026, 3:09 a.m.