Triple
T32746440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaction Control System |
E837365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft attitude control subsystem |
C22743
|
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 attitude control subsystem Context triple: [Reaction Control System, instanceOf, spacecraft attitude control subsystem]
-
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.
aerospace engineering subsystem
chosen
An aerospace engineering subsystem is a specialized, interrelated component or functional unit within an aerospace vehicle or system (such as propulsion, avionics, or thermal control) that performs a distinct set of engineering tasks to support overall mission objectives.
-
C.
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.
-
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.
Spacelab subsystem
A Spacelab subsystem is a distinct functional component of the Spacelab space laboratory that performs specialized tasks—such as power, life support, data handling, or experiment support—to enable and sustain scientific operations in orbit.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.