Triple
T23599657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 mission team |
E582717
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NASA mission team |
C31045
|
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: NASA mission team Context triple: [Apollo 11 mission team, instanceOf, NASA mission team]
-
A.
space mission science team
chosen
A space mission science team is a multidisciplinary group of scientists and specialists responsible for defining mission objectives, designing experiments, analyzing data, and interpreting scientific results to achieve the mission’s research goals.
-
B.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
C.
NASA space mission
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.
-
D.
NASA spacecraft program
A NASA spacecraft program is an organized initiative that designs, develops, launches, and operates one or more spacecraft to achieve specific scientific, exploratory, or technological objectives in space.
-
E.
NASA network
A NASA network is an interconnected system of communication, data, and computing resources that links NASA’s spacecraft, ground stations, research centers, and partner organizations to support space missions and scientific operations.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:43 p.m.