Triple
T9808062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuttle Remote Manipulator System |
E238201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spaceborne 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: spaceborne robotic arm Context triple: [Shuttle Remote Manipulator System, instanceOf, spaceborne robotic arm]
-
A.
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.
-
B.
Mars rover instrument
A Mars rover instrument is a specialized scientific device mounted on a Mars rover that measures, analyzes, or images the Martian environment and geology to support planetary research and exploration objectives.
-
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.
NASA ground support equipment
NASA ground support equipment comprises the specialized tools, structures, and systems used on the ground to assemble, test, transport, service, and launch spacecraft and launch vehicles safely and reliably.
- F. None of above. chosen
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.