Triple

T19372865
Position Surface form Disambiguated ID Type / Status
Subject Pavel Sukhoi E484587 entity
Predicate designed P184 FINISHED
Object Sukhoi Su-9 NE NERFINISHED

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: Sukhoi Su-9 | Statement: [Pavel Sukhoi, designed, Sukhoi Su-9]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sukhoi Su-9
Context triple: [Pavel Sukhoi, designed, Sukhoi Su-9]
  • A. Su-9 chosen
    The Su-9 was a Soviet supersonic jet interceptor aircraft developed in the 1950s for high-speed, high-altitude air defense missions.
  • B. Sukhoi Su-7
    The Sukhoi Su-7 is a Soviet-era swept-wing fighter-bomber aircraft widely used during the Cold War for ground-attack missions.
  • C. Sukhoi Su-2
    The Sukhoi Su-2 was a Soviet single-engine light bomber and reconnaissance aircraft used primarily in the early years of World War II on the Eastern Front.
  • D. Su-11
    The Su-11 was a Soviet supersonic interceptor aircraft developed in the early Cold War era to defend Soviet airspace against high-altitude threats.
  • E. Mikoyan-Gurevich MiG-9
    The Mikoyan-Gurevich MiG-9 was the Soviet Union’s first operational jet fighter, entering service shortly after World War II and marking the beginning of the MiG jet fighter lineage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619b1b5fc819089f9fc43f407bbb0 completed April 20, 2026, 12:18 p.m.
Created at: April 10, 2026, 1:35 p.m.