Triple
T24453078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitley Mk III |
E616600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armstrong Whitworth Whitley variant |
C49027
|
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: Armstrong Whitworth Whitley variant Context triple: [Whitley Mk III, instanceOf, Armstrong Whitworth Whitley variant]
-
A.
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.
-
B.
Hawker Hurricane variant
A Hawker Hurricane variant is a specific model or modification of the original British single-seat fighter aircraft, distinguished by changes in engine, armament, structure, or role to meet evolving operational requirements.
-
C.
Bristol Blenheim variant
A Bristol Blenheim variant is a specific model or modification of the British twin‑engine light bomber and reconnaissance aircraft, distinguished by changes in features such as engines, armament, equipment, or airframe configuration.
-
D.
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.
-
E.
Gloster Meteor variant
A Gloster Meteor variant is a specific model or modification of the original British twin‑jet fighter, distinguished by changes in design, equipment, or role to meet particular operational requirements.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:18 a.m.