Triple

T25849188
Position Surface form Disambiguated ID Type / Status
Subject Siege of Nicosia (1570) E651153 entity
Predicate instanceOf P0 FINISHED
Object event in the Ottoman–Venetian War (1570–1573) C43663 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: event in the Ottoman–Venetian War (1570–1573)
Context triple: [Siege of Nicosia (1570), instanceOf, event in the Ottoman–Venetian War (1570–1573)]
  • A. event in the Byzantine–Ottoman wars
    An "event in the Byzantine–Ottoman wars" is a specific historical occurrence—such as a battle, siege, treaty, or political development—that took place within the broader series of conflicts between the Byzantine Empire and the Ottoman state.
  • B. Ottoman–Venetian War event chosen
    An Ottoman–Venetian War event represents a specific historical occurrence—such as a battle, siege, treaty, or campaign—arising from the series of military conflicts between the Ottoman Empire and the Republic of Venice.
  • C. event in the Dutch–Portuguese War
    An event in the Dutch–Portuguese War is a specific military, political, or diplomatic occurrence between 1602 and 1663 involving Dutch and Portuguese forces or authorities that influenced the course or outcome of their global conflict.
  • D. event in the Ottoman Empire
    An event in the Ottoman Empire is any significant occurrence—political, military, social, economic, or cultural—that took place within or directly affected the Ottoman state and its territories during its existence.
  • E. Habsburg–Ottoman War event
    A Habsburg–Ottoman War event represents a specific military, political, or diplomatic occurrence within the broader conflicts between the Habsburg Monarchy and the Ottoman Empire, characterized by its participants, location, date, and historical impact.
  • 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_69e7ab39035c8190be15c8aaee1bb858 completed April 21, 2026, 4:52 p.m.
Created at: April 22, 2026, 7:58 a.m.