Triple
T36485373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Standard Payload Rack |
E898920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station payload rack |
C53103
|
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 payload rack Context triple: [International Standard Payload Rack, instanceOf, space station payload rack]
-
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.
International Space Station hardware
chosen
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.
-
C.
International Space Station truss segment
An International Space Station truss segment is a structural module that forms part of the station’s backbone, supporting solar arrays, radiators, and utilities while providing attachment points and routing for power, data, and thermal control systems.
-
D.
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.
-
E.
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.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.