Triple
T13546595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis launch vehicles |
E323527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heavy-lift launch vehicles |
C3706
|
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: heavy-lift launch vehicles Context triple: [Artemis launch vehicles, instanceOf, heavy-lift launch vehicles]
-
A.
heavy-lift launch vehicle
chosen
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.
-
B.
super heavy-lift launch vehicle
A super heavy-lift launch vehicle is a powerful rocket system designed to carry extremely large payloads—such as crewed spacecraft, space station modules, or deep-space missions—into Earth orbit or beyond in a single launch.
-
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.
medium-lift launch vehicle
A medium-lift launch vehicle is a rocket system designed to place a moderate payload mass—typically several tons—into low Earth orbit or higher orbits, balancing performance and cost between small and heavy-lift launchers.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:45 p.m.