Triple
T36484991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robotics Workstation |
E898912
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station subsystem |
C36605
|
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 subsystem Context triple: [Robotics Workstation, instanceOf, space station subsystem]
-
A.
Space Shuttle subsystem
A Space Shuttle subsystem is a distinct functional component or collection of components within the Space Shuttle that performs a specific role—such as propulsion, life support, guidance, or power management—to enable safe and effective mission operations.
-
B.
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.
-
C.
International Space Station hardware
Physical components and systems that make up, support, and enable the operation of the International Space Station, including its structure, modules, instruments, and onboard equipment.
-
D.
spacecraft propulsion subsystem
A spacecraft propulsion subsystem is the integrated set of components and control mechanisms that generate and manage thrust to maneuver, orient, and adjust the trajectory of a spacecraft throughout its mission.
-
E.
space station segment group
chosen
A space station segment group is a collection of interconnected modules or structural elements that function together as a cohesive subsystem within a larger space station.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.