Triple

T12852383
Position Surface form Disambiguated ID Type / Status
Subject 2018 Kerch Strait incident E307356 entity
Predicate instanceOf P0 FINISHED
Object Russo-Ukrainian War event C5517 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: Russo-Ukrainian War event
Context triple: [2018 Kerch Strait incident, instanceOf, Russo-Ukrainian War event]
  • A. event in the Russo-Ukrainian War chosen
    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.
  • B. European war
    A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
  • C. invasion of Russia
    Invasion of Russia is a large-scale military campaign in which foreign forces attempt to penetrate, occupy, or subdue Russian territory, often facing vast distances, harsh climate, and strong defensive resistance.
  • D. 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.
  • E. campaign of the Russian Civil War
    A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
Created at: April 9, 2026, 5:36 p.m.