Triple
T24758566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LV907 |
E619363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Handley Page Halifax bomber |
C21384
|
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: Handley Page Halifax bomber Context triple: [LV907, instanceOf, Handley Page Halifax bomber]
-
A.
Avro Lancaster bomber
The Avro Lancaster bomber was a British four‑engined heavy bomber of World War II, renowned for its large payload capacity, long range, and pivotal role in strategic night bombing campaigns over Europe.
-
B.
Handley Page Halifax variant
chosen
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.
-
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.
Armstrong Whitworth Whitley variant
The Armstrong Whitworth Whitley variant is a specific model or modification of the British twin-engine, long-range heavy bomber aircraft used primarily by the Royal Air Force during the early years of World War II.
-
E.
Avro Vulcan
The Avro Vulcan is a British delta-wing strategic bomber developed in the 1950s, renowned for its distinctive shape, nuclear deterrent role during the Cold War, and later use in long-range conventional bombing missions.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:26 a.m.