Triple
T12178484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempest Mk V |
E290154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hawker Tempest variant |
C31033
|
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: Hawker Tempest variant Context triple: [Tempest Mk V, instanceOf, Hawker Tempest variant]
-
A.
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.
-
B.
Supermarine Swift variant
A Supermarine Swift variant is a specific model within the Supermarine Swift family of British jet fighter and reconnaissance aircraft, distinguished by particular modifications in design, equipment, or role.
-
C.
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).
-
D.
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.
-
E.
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.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.