Triple
T24292586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Ministry Specification B.3/34 |
E605863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aircraft requirement |
C48654
|
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: military aircraft requirement Context triple: [Air Ministry Specification B.3/34, instanceOf, military aircraft requirement]
-
A.
military aircraft
A military aircraft is a powered flying vehicle specifically designed, equipped, and operated by armed forces to conduct combat, support, reconnaissance, or training missions in defense and warfare operations.
-
B.
fighter aircraft
A fighter aircraft is a fast, highly maneuverable military airplane designed primarily to secure air superiority by engaging and destroying enemy aircraft in combat.
-
C.
research aircraft
A research aircraft is a specially equipped airplane or other flying vehicle used to conduct scientific experiments, test new aviation technologies, and gather atmospheric or aerodynamic data.
-
D.
fighter aircraft upgrade configuration
A fighter aircraft upgrade configuration is a defined set of modifications, systems, and software enhancements applied to an existing fighter platform to improve its performance, capabilities, survivability, or mission adaptability.
-
E.
reconnaissance aircraft
A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.