Triple
T18861169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i-Cockpit interior design |
E461313
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cockpit layout |
C20345
|
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: cockpit layout Context triple: [i-Cockpit interior design, instanceOf, cockpit layout]
-
A.
aircraft control system layout
chosen
The aircraft control system layout defines the physical and logical arrangement of all control components, linkages, and interfaces that transmit pilot or automated inputs to the aircraft’s control surfaces and systems.
-
B.
avionics system
An avionics system is an integrated collection of electronic hardware and software on an aircraft that manages navigation, communication, monitoring, and control functions to ensure safe and efficient flight operations.
-
C.
flight simulation facility
A flight simulation facility is a specialized environment equipped with advanced simulators and support systems that replicate real-world aircraft operations for pilot training, research, and systems testing.
-
D.
integrated avionics suite
An integrated avionics suite is a cohesive collection of aircraft electronic systems—such as navigation, communication, flight control, and monitoring—designed to work together through shared hardware, software, and data networks to enhance safety, efficiency, and pilot situational awareness.
-
E.
aviation component
An aviation component is an individual part or subsystem designed, manufactured, and certified to perform a specific function within an aircraft or related aerospace system.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.