Triple
T11692400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commercial Resupply Services 1 |
E277900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cargo resupply mission |
C14432
|
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: cargo resupply mission Context triple: [Commercial Resupply Services 1, instanceOf, cargo resupply mission]
-
A.
rescue mission
A rescue mission is a coordinated operation undertaken to locate, assist, and safely extract individuals or groups from dangerous or life-threatening situations.
-
B.
space station resupply vehicle
chosen
A space station resupply vehicle is a spacecraft designed to transport cargo, equipment, and sometimes crew to and from an orbiting space station, supporting its ongoing operations and maintenance.
-
C.
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.
-
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.
space mission rideshare platform
A space mission rideshare platform is a digital marketplace that connects satellite operators and payload customers with available launch capacity on rockets, enabling shared missions, cost savings, and streamlined logistics for accessing 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.