Triple
T16720010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Orbiter |
E406322
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite launch proposal |
C25838
|
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: satellite launch proposal Context triple: [Project Orbiter, instanceOf, satellite launch proposal]
-
A.
orbital launch attempt
An orbital launch attempt is a specific mission event in which a launch vehicle is prepared, fueled, and commanded to ascend with the objective of placing a payload into a stable orbit around a celestial body.
-
B.
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.
-
C.
space infrastructure project
A space infrastructure project is a large-scale, coordinated initiative to design, build, and operate physical and digital systems that enable sustained activities and services in space, such as communication, transportation, energy, and research.
-
D.
space launch procurement program
chosen
A space launch procurement program is an organized framework through which a government or commercial entity acquires launch services, vehicles, and related support to place payloads into space under defined technical, schedule, and cost requirements.
-
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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.