Triple
T33678841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-6DU |
E862837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variant of the Xian H-6 bomber |
C58396
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variant of the Xian H-6 bomber Context triple: [H-6DU, instanceOf, variant of the Xian H-6 bomber]
-
A.
Xian H-6 variant
chosen
The Xian H-6 variant is a Chinese twin‑engine, long‑range strategic bomber derived from the Soviet Tu‑16, produced in multiple upgraded versions for roles including nuclear strike, conventional attack, and missile carriage.
-
B.
bomber aircraft variant
A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
-
C.
variant of Mil Mi-10
A variant of the Mil Mi-10 is a specialized version of the Soviet heavy-lift helicopter tailored with modified equipment, structure, or performance features to fulfill distinct transport or support roles.
-
D.
MiG-29 derivative
A MiG-29 derivative is any aircraft design or variant that evolves from the original MiG-29 Fulcrum platform, incorporating modifications in structure, avionics, propulsion, or mission role while retaining its core aerodynamic and design lineage.
-
E.
Lockheed Hudson variant
A Lockheed Hudson variant is a specific model or modification of the Lockheed Hudson twin‑engine light bomber and maritime patrol aircraft, distinguished by particular equipment, performance characteristics, or mission adaptations.
- F. None of above.
Provenance (1 batch)
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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.