Triple

T7277338
Position Surface form Disambiguated ID Type / Status
Subject Siege of Sarajevo E163062 entity
Predicate instanceOf P0 FINISHED
Object event in the Bosnian War C20667 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 Bosnian War
Context triple: [Siege of Sarajevo, instanceOf, event in the Bosnian War]
  • A. event in the Syrian civil war
    An event in the Syrian civil war is a specific, temporally and geographically bounded incident—such as a battle, airstrike, protest, ceasefire, or diplomatic action—that significantly affects the course, dynamics, or humanitarian conditions of the conflict.
  • B. event in Serbian history
    A significant occurrence or development within the historical timeline of Serbia that influenced its political, social, cultural, or territorial evolution.
  • C. event in the Crimean War
    An event in the Crimean War is a specific historical occurrence—such as a battle, diplomatic action, military maneuver, or political decision—that took place between 1853 and 1856 and contributed to the course and outcome of the conflict.
  • D. event in the Russo-Ukrainian War
    An event in the Russo-Ukrainian War is a specific, temporally and geographically bounded occurrence—such as a battle, diplomatic action, territorial change, or significant incident—that affects the course, perception, or outcomes of the conflict.
  • E. event in the Franco-Spanish War
    An event in the Franco-Spanish War is a specific historical occurrence—such as a battle, treaty, siege, or political decision—that took place between France and Spain during their 17th-century conflicts and significantly influenced the course or outcome of the war.
  • 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_69c6885c5964819085b209701769877f completed March 27, 2026, 1:38 p.m.
Created at: March 27, 2026, 2:59 p.m.