Triple
T17390949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 551 |
E422820
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | expendable launch system configuration |
C3403
|
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 launch system configuration Context triple: [Atlas V 551, instanceOf, expendable launch system configuration]
-
A.
expendable launch system
chosen
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.
-
B.
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.
-
C.
expendable launch vehicle family
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.
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.
-
E.
space launch vehicle component
A space launch vehicle component is a physical subsystem or part—such as engines, tanks, avionics, or structural elements—that contributes to the propulsion, guidance, structural integrity, or support functions required to deliver payloads from Earth to space.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:45 a.m.