Triple
T10845833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L110 |
E256006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | launch vehicle upper structure |
C28889
|
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 vehicle upper structure Context triple: [L110, instanceOf, launch vehicle upper structure]
-
A.
rocket upper stage
A rocket upper stage is the final propulsion segment of a launch vehicle, designed to operate in near-vacuum conditions to place payloads into their intended orbits or trajectories after lower stages have completed initial ascent.
-
B.
expendable launch vehicle stage
An expendable launch vehicle stage is a non-reusable rocket segment that houses propulsion, propellant, and associated systems, designed to operate for a specific phase of flight and then be discarded once its fuel is depleted.
-
C.
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.
-
D.
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.
-
E.
expendable launch system
An expendable launch system is a type of launch vehicle designed for a single use, where major components are not recovered after delivering payloads such as satellites or spacecraft into orbit or on a trajectory.
- F. None of above. chosen
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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.