Triple
T34713967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion avionics |
E1000723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | guidance navigation and control system |
C7919
|
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: guidance navigation and control system Context triple: [Orion avionics, instanceOf, guidance navigation and control system]
-
A.
missile guidance and control system
A missile guidance and control system is an integrated set of sensors, processors, and actuators that continuously determines a missile’s position and trajectory and adjusts its flight path to accurately reach a designated target.
-
B.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
C.
attitude control computer
chosen
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.
-
D.
missile guidance stage
A missile guidance stage is the phase or subsystem of a missile’s flight during which onboard sensors and control algorithms determine and adjust its trajectory to accurately reach a designated target.
-
E.
terrestrial navigation system
A terrestrial navigation system is a ground-based infrastructure and associated equipment that determine a vehicle’s position, velocity, and course using signals or references located on or near the Earth’s surface.
- 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.