Triple
T36483035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-4 |
E898867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apollo program test mission |
C62293
|
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: Apollo program test mission Context triple: [SA-4, instanceOf, Apollo program test mission]
-
A.
Orion program activity
Orion program activity is any discrete task, operation, or event carried out as part of planning, developing, testing, or executing the Orion spacecraft program.
-
B.
Apollo spacecraft variant
An Apollo spacecraft variant is a specific configuration or modification of the Apollo command and service modules, and sometimes the lunar module, tailored to different mission profiles, technological updates, or experimental objectives within the Apollo program.
-
C.
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.
-
D.
Apollo spacecraft equipment
Apollo spacecraft equipment comprises the specialized instruments, life-support systems, navigation and communication devices, and structural components designed to support crewed lunar missions and ensure astronaut safety and mission success.
-
E.
lunar orbiter mission
A lunar orbiter mission is a spaceflight operation in which a spacecraft is placed into orbit around the Moon to conduct sustained observations, measurements, and communications for scientific, exploration, or operational objectives.
- F. None of above. chosen
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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.