Triple
T32197067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APAS |
E822429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft docking mechanism |
C10281
|
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 docking mechanism Context triple: [APAS, instanceOf, spacecraft docking mechanism]
-
A.
spacecraft docking system
chosen
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.
-
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 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.
-
D.
spaceborne robotic arm
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.
-
E.
modular spacecraft
A modular spacecraft is a reconfigurable space vehicle composed of interchangeable, standardized modules that can be assembled, upgraded, or replaced to support different missions and functions.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:36 a.m.