Triple
T35724591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N1 lunar rocket program |
E1032571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | super-heavy launch vehicle development program |
C2828
|
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: super-heavy launch vehicle development program Context triple: [N1 lunar rocket program, instanceOf, super-heavy launch vehicle development program]
-
A.
super heavy-lift launch vehicle
chosen
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.
-
B.
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.
-
C.
space launch vehicle development program
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.
-
D.
proposed launch vehicle
A proposed launch vehicle is a conceptual or preliminary design for a rocket system intended to transport payloads from Earth’s surface into space, but not yet built or operational.
-
E.
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.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.