Triple
T9413711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Duration Propulsive EELV Secondary Payload Adapter |
E226763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | orbital transfer and hosting vehicle |
C2826
|
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: orbital transfer and hosting vehicle Context triple: [Long Duration Propulsive EELV Secondary Payload Adapter, instanceOf, orbital transfer and hosting vehicle]
-
A.
orbital launch vehicle
An orbital launch vehicle is a rocket-powered system designed to transport payloads from Earth's surface into orbit by achieving sufficient velocity and altitude to remain in continuous free-fall around the planet.
-
B.
orbital test vehicle
An orbital test vehicle is a reusable or expendable spacecraft designed to conduct experimental missions in Earth orbit to validate technologies, systems, or operational concepts for future spaceflight applications.
-
C.
space station resupply vehicle
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.
-
D.
spacecraft
chosen
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
-
E.
expendable launch vehicle
An expendable launch vehicle is a rocket designed for a single use to deliver payloads such as satellites or spacecraft into space, after which its components are discarded rather than recovered or reused.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:47 p.m.