Triple

T235265
Position Surface form Disambiguated ID Type / Status
Subject U-2 incident of 1960 E4495 entity
Predicate SovietResponse P3843 FINISHED
Object publicly revealed captured pilot and wreckage LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: publicly revealed captured pilot and wreckage | Statement: [U-2 incident of 1960, SovietResponse, publicly revealed captured pilot and wreckage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: SovietResponse
Context triple: [U-2 incident of 1960, SovietResponse, publicly revealed captured pilot and wreckage]
  • A. SovietAction chosen
    Indicates actions, policies, or interventions carried out by the Soviet Union or its authorities toward another entity.
  • B. hasSovietLeaderParticipant
    Indicates that a Soviet leader is a participant in the referenced event, action, or relationship.
  • C. establishedAsSocialistState
    Indicates that an entity formally created or declared another entity to be a socialist state as its system of governance.
  • D. numberOfSovietPOWsVictimsEstimate
    Indicates an estimated count of victims who were Soviet prisoners of war.
  • E. statusDuringColdWar
    Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
  • F. None of above.

Provenance (3 batches)

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_69a257363ffc81909757bde7ab3404da completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25cc9ab2c81909af278a07f86aa1e completed Feb. 28, 2026, 3:11 a.m.
PD Predicate disambiguation batch_69a25b5dc640819092669575731c393f completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:53 a.m.