Triple

T16628762
Position Surface form Disambiguated ID Type / Status
Subject J-8 E404019 entity
Predicate usesAbbreviation P43 FINISHED
Object J-8 E404019 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: J-8 | Statement: [J-8, usesAbbreviation, J-8]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: J-8
Context triple: [J-8, usesAbbreviation, J-8]
  • A. J-8 chosen
    J-8 is the Joint Staff directorate responsible for force structure, resources, and assessment within the U.S. Department of Defense.
  • B. Hongdu JL-8
    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.
  • C. 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.
  • D. Xian WS-9
    The Xian WS-9 is a Chinese-built turbofan aircraft engine produced under license from the British Rolls-Royce Spey design.
  • E. Shenyang J-11BS
    The Shenyang J-11BS is a Chinese twin-seat, multirole fighter aircraft developed as a domestically produced variant of the Russian Su-27, used primarily for training and combat missions by the People's Liberation Army Air Force.
  • 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_69d883897eb481909eaaa088ba9918d9 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e378e399988190904e56eb3c490eed completed April 18, 2026, 12:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a007dbc6cf48190879b25e66c9453db completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:17 a.m.