Triple

T13946029
Position Surface form Disambiguated ID Type / Status
Subject GSh-30-2 E335386 entity
Predicate usedOnAircraft P10706 FINISHED
Object Su-17M4 E322953 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-17M4 | Statement: [GSh-30-2, usedOnAircraft, Su-17M4]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Su-17M4
Context triple: [GSh-30-2, usedOnAircraft, Su-17M4]
  • A. Su-17 chosen
    The Su-17 is a Soviet variable-sweep wing fighter-bomber developed from the Su-7 and widely used for ground-attack and strike missions during the Cold War.
  • 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-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.
  • E. 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.
  • 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_69d81c6081b88190b53e317c3370c8fe completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2e10f60c81908ee9636e85c070ff completed April 14, 2026, 12:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd27f8f388819096c7c33b90f9ac4c completed May 8, 2026, 12:02 a.m.
Created at: April 9, 2026, 10:17 p.m.