Triple

T10424629
Position Surface form Disambiguated ID Type / Status
Subject Xian H-6 E245753 entity
Predicate variant P4680 FINISHED
Object H‑6U E862837 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: H‑6U | Statement: [Xian H-6, variant, H‑6U]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: H‑6U
Context triple: [Xian H-6, variant, H‑6U]
  • A. H‑6A
    The H‑6A is an early Chinese strategic bomber variant developed from the Xian H‑6, primarily used for long-range conventional and nuclear strike roles.
  • B. H‑6J
    The H‑6J is a modernized Chinese long-range maritime strike bomber variant equipped with advanced avionics and anti-ship capabilities, operated primarily by the People's Liberation Army Navy.
  • C. H‑6N
    The H‑6N is a modern Chinese long-range strategic bomber variant reportedly capable of carrying air-launched ballistic missiles and other advanced stand-off weapons.
  • D. H‑6DU chosen
    H‑6DU is a modernized Chinese H-6 bomber variant configured primarily as an aerial refueling tanker to extend the range of other combat aircraft.
  • E. H‑6H
    The H‑6H is a modernized Chinese H-6 bomber variant equipped for long-range precision strike missions, including the deployment of cruise missiles.
  • 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_69d381bf3dc08190bf35a2643e4e8f22 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4ea47a6408190a87b32760692487f completed April 7, 2026, 11:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69d90d92510481909135a75b2f582795 completed April 10, 2026, 2:47 p.m.
Created at: April 6, 2026, 12:12 p.m.