Triple
T10999934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobile Base System |
E259978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station external payload facility |
C11468
|
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 external payload facility Context triple: [Mobile Base System, instanceOf, space station external payload facility]
-
A.
ISS external payload
chosen
An ISS external payload is a scientific or technological instrument package mounted on the outside of the International Space Station to conduct experiments, observations, or demonstrations in the space environment.
-
B.
Space Shuttle payload module
A Space Shuttle payload module is a specialized, modular structure designed to house, support, and interface scientific instruments, cargo, or satellites within the Shuttle’s payload bay for deployment or on-orbit operations.
-
C.
spacecraft payload adapter
A spacecraft payload adapter is a structural interface that securely connects a satellite or payload to the launch vehicle, ensuring proper alignment, load transfer, and separation during ascent and deployment.
-
D.
space station resupply vehicle
A space station resupply vehicle is a spacecraft designed to transport cargo, equipment, and sometimes crew to and from an orbiting space station, supporting its ongoing operations and maintenance.
-
E.
Space Shuttle payload handling system
A Space Shuttle payload handling system is the integrated set of mechanical, electronic, and software components used to secure, manipulate, deploy, and retrieve payloads within the orbiter’s payload bay during space missions.
- 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.