Triple
T34713968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion avionics |
E1000723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | onboard flight control system |
C14046
|
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: onboard flight control system Context triple: [Orion avionics, instanceOf, onboard flight control system]
-
A.
attitude control computer
An attitude control computer is an onboard system that calculates and commands the necessary control actions to orient and stabilize a vehicle, such as a spacecraft or aircraft, in three-dimensional space.
-
B.
aircraft control system layout
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.
-
C.
avionics system
chosen
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.
-
D.
spacecraft onboard computer
A spacecraft onboard computer is a specialized, radiation-hardened computing system that autonomously manages spacecraft functions, navigation, communication, and data handling in the harsh environment of space.
-
E.
Instrument landing system
An instrument landing system is a ground-based radio navigation aid that provides precise lateral and vertical guidance to aircraft approaching and landing on a runway, especially in low-visibility conditions.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.