Triple
T17326277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed Model 82 design studies |
E420694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conceptual aircraft design |
C17298
|
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: conceptual aircraft design Context triple: [Lockheed Model 82 design studies, instanceOf, conceptual aircraft design]
-
A.
blended wing body aircraft
A blended wing body aircraft is a fixed-wing air vehicle whose wings and fuselage form a continuous, integrated lifting surface to improve aerodynamic efficiency, fuel economy, and internal volume.
-
B.
aircraft designer
An aircraft designer is a professional who conceptualizes, plans, and develops the structure, systems, and performance characteristics of airplanes and other flying vehicles to meet safety, efficiency, and mission requirements.
-
C.
delta‑wing aircraft
A delta-wing aircraft is a fixed-wing airplane whose wings form a triangular, swept-back planform that provides high-speed performance, structural simplicity, and good maneuverability, especially at high angles of attack.
-
D.
design wing
chosen
A design wing is a specialized division within an organization dedicated to conceptualizing, developing, and refining creative solutions, products, or visual identities.
-
E.
aerodynamic technology
Aerodynamic technology encompasses the principles, tools, and systems used to control and optimize the behavior of air and other gases around objects to reduce drag, increase efficiency, and improve performance in applications such as aviation, automotive design, and wind engineering.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:43 a.m.