Triple
T25642984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Shepard booster |
E642881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reusable suborbital rocket stage |
C3271
|
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: reusable suborbital rocket stage Context triple: [New Shepard booster, instanceOf, reusable suborbital rocket stage]
-
A.
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.
-
B.
prototype rocket stage
A prototype rocket stage is an experimental segment of a launch vehicle, typically containing structure, propulsion, and control systems, built and tested to validate design concepts and performance before full-scale production.
-
C.
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.
-
D.
partially reusable launch vehicle
chosen
A partially reusable launch vehicle is a space launch system in which only some components—such as the first stage, boosters, or engines—are recovered and refurbished for multiple flights, while the remaining parts are expended.
-
E.
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.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 5:46 p.m.