Triple
T10502399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-400 |
E247703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | launch-on-need mission |
C8801
|
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: launch-on-need mission Context triple: [STS-400, instanceOf, launch-on-need mission]
-
A.
space mission
chosen
A space mission is a planned and coordinated endeavor to send spacecraft, instruments, or humans beyond Earth's atmosphere to achieve specific scientific, exploratory, commercial, or technological objectives.
-
B.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
C.
Long Duration Propulsive EELV Secondary Payload Adapter mission
A Long Duration Propulsive EELV Secondary Payload Adapter mission is a spaceflight that uses a propulsive ESPA ring on an Evolved Expendable Launch Vehicle to carry and operate secondary payloads for extended periods in space, providing independent maneuvering and mission flexibility separate from the primary payload.
-
D.
rideshare payload adapter mission
A rideshare payload adapter mission is a launch operation that uses a specialized structural interface to mount, support, and deploy multiple small satellites or payloads on a single rocket, enabling shared access to space.
-
E.
SpaceX mission
A SpaceX mission is a coordinated aerospace operation conducted by SpaceX to transport payloads or crew to specific destinations in space, such as Earth orbit, the International Space Station, or beyond.
- 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.