Triple
T5817464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury-Redstone 3 |
E129022
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Project Mercury mission |
C7207
|
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: Project Mercury mission Context triple: [Mercury-Redstone 3, instanceOf, Project Mercury mission]
-
A.
lunar landing mission
A lunar landing mission is a coordinated spaceflight operation designed to transport a spacecraft from Earth to the Moon, achieve a controlled descent and landing on the lunar surface, conduct scientific or exploratory activities, and safely return data and/or crew.
-
B.
NASA space mission
chosen
A NASA space mission is a coordinated, goal-driven endeavor planned and executed by NASA to explore, observe, or utilize space using specialized spacecraft, instruments, and supporting ground operations.
-
C.
Space Shuttle mission
A Space Shuttle mission is a coordinated spaceflight operation using the Space Shuttle orbiter to transport crew, cargo, and conduct scientific or technical objectives in Earth orbit and beyond.
-
D.
human spaceflight program
A human spaceflight program is an organized, long-term governmental or commercial initiative that designs, funds, and operates crewed missions beyond Earth’s atmosphere for exploration, research, and related objectives.
-
E.
space mission
A space mission is a planned and coordinated endeavor to send spacecraft, instruments, or humans beyond Earth's atmosphere to achieve specific scientific, exploratory, commercial, or technological objectives.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:53 p.m.