Triple
T15858471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Mk IIC |
E384520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hawker Hurricane variant |
C36553
|
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 Hurricane variant Context triple: [Hurricane Mk IIC, instanceOf, Hawker Hurricane 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.
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.
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.
-
D.
Hawker Tempest variant
A Hawker Tempest variant is a specific model or sub-type of the British Hawker Tempest fighter aircraft distinguished by particular design features, performance characteristics, or operational roles.
-
E.
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.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.