Triple
T10037712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbital Maneuvering System |
E205214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle subsystem |
C27328
|
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 Shuttle subsystem Context triple: [Orbital Maneuvering System, instanceOf, Space Shuttle subsystem]
-
A.
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.
-
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.
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.
-
D.
Space Shuttle payload
A Space Shuttle payload is any cargo, equipment, satellite, experiment, or module carried in the Shuttle’s payload bay to be deployed, operated, or returned from space.
-
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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.