Triple
T19307768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuttle Student Involvement Program experiments |
E482884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student-designed spaceflight experiment program |
C22992
|
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: student-designed spaceflight experiment program Context triple: [Shuttle Student Involvement Program experiments, instanceOf, student-designed spaceflight experiment program]
-
A.
spaceflight education initiative
chosen
A spaceflight education initiative is a coordinated program designed to teach learners about space science, technology, and exploration through curricula, hands-on activities, and outreach experiences.
-
B.
space experiment
A space experiment is a controlled scientific investigation conducted in the unique conditions of outer space or microgravity to study physical, biological, or technological phenomena not observable or easily replicated on Earth.
-
C.
space camp
A space camp is an educational program where participants engage in hands-on activities and simulations to learn about space science, astronomy, and astronaut training.
-
D.
spacecraft program
A spacecraft program is an organized, long-term initiative that plans, develops, launches, and operates one or more spacecraft to achieve specific scientific, commercial, or exploratory objectives.
-
E.
spaceflight participant
A spaceflight participant is a non-professional individual who travels into space, typically as a tourist, researcher, or guest, without serving as a career astronaut or cosmonaut.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:32 p.m.