Triple

T23534787
Position Surface form Disambiguated ID Type / Status
Subject Ivchenko AI-25 E576669 entity
Predicate usedOnAircraft P10706 FINISHED
Object Hongdu JL-8 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: Hongdu JL-8 | Statement: [Ivchenko AI-25, usedOnAircraft, Hongdu JL-8]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hongdu JL-8
Context triple: [Ivchenko AI-25, usedOnAircraft, Hongdu JL-8]
  • A. Hongdu JL-8 chosen
    The Hongdu JL-8 is a Chinese-designed jet trainer and light attack aircraft developed to provide an affordable, modern training platform for fighter pilots.
  • B. J-8
    J-8 is the Joint Staff directorate responsible for force structure, resources, and assessment within the U.S. Department of Defense.
  • C. Xian WS-9
    The Xian WS-9 is a Chinese-built turbofan aircraft engine produced under license from the British Rolls-Royce Spey design.
  • D. Xian JH-7
    The Xian JH-7 is a Chinese twin-engine fighter-bomber designed for long-range strike missions, particularly in maritime attack roles.
  • E. La-15 jet fighter
    The La-15 jet fighter was a Soviet early-generation swept-wing jet interceptor developed in the late 1940s as one of the USSR’s first operational jet fighters.
  • 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ae164f348190a6bde1a0dfc66389 completed April 29, 2026, 7:07 a.m.
Created at: April 17, 2026, 6:10 p.m.