Triple
T10923547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do 17E |
E258005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dornier Do 17 variant |
C28566
|
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: Dornier Do 17 variant Context triple: [Do 17E, instanceOf, Dornier Do 17 variant]
-
A.
Messerschmitt Me 262 variant
A Messerschmitt Me 262 variant is a specific model or modification of the German World War II jet fighter, distinguished by changes in armament, engines, airframe, or operational role.
-
B.
de Havilland Mosquito variant
A de Havilland Mosquito variant is a specific model of the twin‑engine, multi‑role World War II aircraft distinguished by particular modifications to its structure, equipment, or mission profile (such as fighter, bomber, reconnaissance, or night fighter roles).
-
C.
Vickers Wellington variant
A Vickers Wellington variant is a specific model or modification of the British twin‑engine Wellington bomber, distinguished by changes in equipment, structure, or role to meet particular operational requirements.
-
D.
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.
-
E.
Handley Page Halifax variant
A Handley Page Halifax variant is a specific model or modification of the British four‑engined heavy bomber, distinguished by changes in engines, armament, structure, or equipment to fulfill particular operational roles during its service life.
- F. None of above. chosen
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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.