Triple
T13014862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawker P.1040 |
E322523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British military aircraft prototype |
C32330
|
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: British military aircraft prototype Context triple: [Hawker P.1040, instanceOf, British military aircraft prototype]
-
A.
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.
-
B.
British Air Ministry specification
A British Air Ministry specification was an official document issued by the Air Ministry that defined the performance, design, and operational requirements for new military aircraft or equipment to be developed for the Royal Air Force.
-
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.
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.
prototype bomber aircraft
A prototype bomber aircraft is an experimental military airplane built to test and refine new bombing technologies, designs, and capabilities before potential mass production and operational deployment.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:50 p.m.