Triple
T4014506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cygnus spacecraft |
E90723
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commercial resupply spacecraft |
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: commercial resupply spacecraft Context triple: [Cygnus spacecraft, instanceOf, commercial resupply spacecraft]
-
A.
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.
-
B.
reusable spaceplane
A reusable spaceplane is a winged spacecraft designed to take off, operate, and land multiple times like an aircraft while transporting payloads or crew between Earth and space.
-
C.
space services company
A space services company is an organization that provides commercial solutions related to space activities, such as launch services, satellite deployment and operations, in-orbit logistics, data services, and mission support for government, commercial, and research customers.
-
D.
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.
-
E.
SpaceX launch vehicle component
A SpaceX launch vehicle component is a physical subsystem or part—such as engines, tanks, avionics, or structural elements—that integrates with other components to enable the safe, efficient, and reusable operation of a SpaceX rocket during all phases of flight.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.