Triple
T36703699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SM4 |
E906299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Space Shuttle servicing 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 servicing mission Context triple: [SM4, instanceOf, Space Shuttle servicing 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.
spacecraft service module
A spacecraft service module is the section of a spacecraft that houses and provides essential support systems—such as propulsion, power, thermal control, and consumables—to enable and sustain the operation of the crew or payload module.
-
E.
Soyuz TMA-M mission
The Soyuz TMA-M mission is a crewed spaceflight using the modernized Soyuz TMA-M spacecraft to transport astronauts and cosmonauts to and from the International Space Station.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.