Triple
T16807677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briz-M |
E408520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | expendable upper stage |
C22741
|
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: expendable upper stage Context triple: [Briz-M, instanceOf, expendable upper stage]
-
A.
expendable launch vehicle stage
chosen
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.
-
B.
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.
-
C.
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.
-
D.
launch vehicle upper structure
The launch vehicle upper structure is the integrated assembly above the core propulsion stages that houses the payload, guidance systems, and associated support hardware, ensuring structural integrity, environmental protection, and proper deployment during ascent and orbital insertion.
-
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.
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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.