Triple
T34713966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion avionics |
E1000723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft avionics 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: spacecraft avionics system Context triple: [Orion avionics, instanceOf, spacecraft avionics system]
-
A.
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.
-
B.
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.
-
C.
spacecraft safety system
A spacecraft safety system is an integrated set of hardware, software, and procedural controls designed to detect, prevent, and mitigate hazards to protect the vehicle, crew, payload, and mission throughout all phases of spaceflight.
-
D.
spacecraft
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
-
E.
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.
- 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.