Triple
T11000067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSRMS |
E259981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station robotic arm |
C26880
|
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: space station robotic arm Context triple: [SSRMS, instanceOf, space station robotic arm]
-
A.
spaceborne robotic arm
chosen
A spaceborne robotic arm is a remotely operated, articulated mechanical manipulator mounted on a spacecraft or space station, designed to capture, position, and service payloads or structures in the space environment.
-
B.
spacecraft robotic arm
A spacecraft robotic arm is a multi-jointed, computer-controlled manipulator mounted on a spacecraft, used to capture, position, and manipulate objects such as satellites, cargo, or instruments in space.
-
C.
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.
-
D.
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.
-
E.
orbital space station
An orbital space station is a large, habitable artificial structure that continuously orbits a celestial body, serving as a long-term platform for human presence, research, and operations in 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.