Triple
T12254667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariane 5 G |
E292068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ariane 5 variant |
C2214
|
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: Ariane 5 variant Context triple: [Ariane 5 G, instanceOf, Ariane 5 variant]
-
A.
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.
-
B.
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.
-
C.
expendable launch vehicle family
chosen
An expendable launch vehicle family is a series of related, single-use rockets designed to carry payloads into space and then be discarded after each mission.
-
D.
Long Duration Propulsive EELV Secondary Payload Adapter mission
A Long Duration Propulsive EELV Secondary Payload Adapter mission is a spaceflight that uses a propulsive ESPA ring on an Evolved Expendable Launch Vehicle to carry and operate secondary payloads for extended periods in space, providing independent maneuvering and mission flexibility separate from the primary payload.
-
E.
heavy-lift launch vehicle
A heavy-lift launch vehicle is a powerful rocket system designed to carry large payloads—such as satellites, space station modules, or deep-space missions—into orbit or beyond.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.