Triple

T2911766
Position Surface form Disambiguated ID Type / Status
Subject VVS E63696 entity
Predicate operatedAircraftModel P1524 FINISHED
Object Su-7 E65556 NE 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: Su-7 | Statement: [VVS, operatedAircraftModel, Su-7]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Su-7
Context triple: [VVS, operatedAircraftModel, Su-7]
  • A. Sukhoi Su-7 chosen
    The Sukhoi Su-7 is a Soviet-era swept-wing fighter-bomber aircraft widely used during the Cold War for ground-attack missions.
  • B. Su-9
    The Su-9 was a Soviet supersonic jet interceptor aircraft developed in the 1950s for high-speed, high-altitude air defense missions.
  • C. 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.
  • D. Su-22
    The Su-22 is a Soviet-designed variable-sweep wing fighter-bomber widely exported and used for ground-attack missions by several air forces, including Poland’s.
  • E. Su-15
    The Su-15 was a Soviet supersonic interceptor aircraft developed in the 1960s, best known for its role in Cold War air defense and its involvement in several high-profile shootdown incidents.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ab4c44ab448190b9411324e8a1fc1d completed March 6, 2026, 9:51 p.m.
NER Named-entity recognition batch_69abe0ea0ae4819096f17d74072b0b78 completed March 7, 2026, 8:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69b1de8b9378819084861d65dd2b9528 completed March 11, 2026, 9:28 p.m.
Created at: March 6, 2026, 10:11 p.m.