Triple
T7408525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PA474 |
E170940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Avro Lancaster bomber |
C22162
|
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: Avro Lancaster bomber Context triple: [PA474, instanceOf, Avro Lancaster bomber]
-
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.
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.
-
C.
Boulton Paul Defiant variant
A Boulton Paul Defiant variant is any modified version of the British WWII turret-armed fighter aircraft, differing from the base model in aspects such as armament, role, equipment, or structural configuration.
-
D.
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).
-
E.
Panavia Tornado variant
A Panavia Tornado variant is a specific model of the multirole combat aircraft tailored with distinct avionics, structural modifications, and mission equipment to fulfill specialized roles such as strike, reconnaissance, or air defense.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:10 p.m.