Triple
T9936733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helionix glass cockpit |
E193977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | avionics suite |
C14169
|
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: avionics suite Context triple: [Helionix glass cockpit, instanceOf, avionics suite]
-
A.
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.
-
B.
integrated avionics suite
chosen
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.
-
C.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
D.
combat aircraft mission system suite
A combat aircraft mission system suite is an integrated collection of avionics, sensors, communication, navigation, and weapon management subsystems that work together to plan, execute, and support military air missions.
-
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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:44 p.m.