Triple
T24292585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Ministry Specification B.3/34 |
E605863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Air Ministry specification |
C21618
|
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: Air Ministry specification Context triple: [Air Ministry Specification B.3/34, instanceOf, Air Ministry specification]
-
A.
British Air Ministry specification
chosen
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.
-
B.
British military aircraft prototype
A British military aircraft prototype is an experimental or pre-production aircraft developed in the United Kingdom to test and refine new designs, technologies, or capabilities for potential adoption by the armed forces.
-
C.
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.
-
D.
Bristol Blenheim variant
A Bristol Blenheim variant is a specific model or modification of the British twin‑engine light bomber and reconnaissance aircraft, distinguished by changes in features such as engines, armament, equipment, or airframe configuration.
-
E.
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.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.