Triple
T9808063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuttle Remote Manipulator System |
E238201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft manipulator system |
C21609
|
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 manipulator system Context triple: [Shuttle Remote Manipulator System, instanceOf, spacecraft manipulator system]
-
A.
robot control system
chosen
A robot control system is a coordinated set of hardware and software components that interpret sensor data, execute decision-making algorithms, and generate actuator commands to direct a robot’s behavior in real time.
-
B.
spacecraft berthing mechanism
A spacecraft berthing mechanism is a structural and mechanical interface system that enables two spacecraft or modules to be precisely aligned, securely joined, and later separated while maintaining required load paths and connections for power, data, and environmental control.
-
C.
spacecraft docking system
A spacecraft docking system is a coordinated assembly of mechanical interfaces, sensors, and control software that enables two spacecraft to safely approach, align, and connect in orbit for transfer of crew, cargo, or resources.
-
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.
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.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.