Triple
T20340975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Extreme Ultraviolet Hitchhiker |
E495739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space shuttle payload |
C25972
|
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 payload Context triple: [International Extreme Ultraviolet Hitchhiker, instanceOf, space shuttle payload]
-
A.
Space Shuttle payload
chosen
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.
-
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.
NASA payload
A NASA payload is the collection of scientific instruments, technology demonstrations, or mission-specific equipment carried by a spacecraft or launch vehicle to achieve its research and exploration objectives.
-
D.
ISS external payload
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.
-
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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:23 a.m.