Triple
T33754166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-6N |
E864926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | H-6 bomber variant |
C28565
|
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: H-6 bomber variant Context triple: [H-6N, instanceOf, H-6 bomber variant]
-
A.
bomber aircraft variant
chosen
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.
-
B.
Kawasaki Ki-61
The Kawasaki Ki-61 was a Japanese World War II fighter aircraft, notable for its liquid-cooled inline engine and sleek, European-influenced design, used primarily by the Imperial Japanese Army Air Service.
-
C.
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.
-
D.
Dornier Do 217 variant
A Dornier Do 217 variant is a specific model within the German World War II twin-engine bomber and reconnaissance aircraft series, distinguished by modifications in engines, armament, equipment, or structural design to fulfill specialized operational roles.
-
E.
Boeing C-97 Stratofreighter variant
A Boeing C-97 Stratofreighter variant is a specific model derived from the original C-97 military transport aircraft, modified for specialized roles such as aerial refueling, passenger transport, or other mission-specific purposes.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.