Triple
T10502397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-400 |
E247703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle contingency mission |
C5891
|
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 contingency mission Context triple: [STS-400, instanceOf, Space Shuttle contingency mission]
-
A.
Space Shuttle mission
chosen
A Space Shuttle mission is a coordinated spaceflight operation using the Space Shuttle orbiter to transport crew, cargo, and conduct scientific or technical objectives in Earth orbit and beyond.
-
B.
International Space Station expedition
An International Space Station expedition is a long-duration mission during which a designated crew lives and works aboard the ISS to conduct scientific research, perform maintenance, and support ongoing space operations.
-
C.
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.
-
D.
NASA space mission
A NASA space mission is a coordinated, goal-driven endeavor planned and executed by NASA to explore, observe, or utilize space using specialized spacecraft, instruments, and supporting ground operations.
-
E.
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.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:25 p.m.