Triple
T3894349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vega launch vehicle programme |
E88134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European space launch programme |
C12851
|
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: European space launch programme Context triple: [Vega launch vehicle programme, instanceOf, European space launch programme]
-
A.
space launch vehicle development program
chosen
A space launch vehicle development program is an organized, multi-phase effort to design, test, and qualify rockets and associated systems for reliably delivering payloads from Earth to space.
-
B.
human spaceflight program
A human spaceflight program is an organized, long-term governmental or commercial initiative that designs, funds, and operates crewed missions beyond Earth’s atmosphere for exploration, research, and related objectives.
-
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.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.