Triple
T36847955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Jet Propulsion Laboratory programs |
E910602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | robotic space mission portfolio |
C29715
|
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: robotic space mission portfolio Context triple: [NASA Jet Propulsion Laboratory programs, instanceOf, robotic space mission portfolio]
-
A.
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.
-
B.
Mars mission engineering activity
Mars mission engineering activity encompasses the planning, design, testing, and integration of systems and technologies required to safely transport, land, and support missions on the Martian surface and in its orbit.
-
C.
Mars mission element
A Mars mission element is a distinct component, system, or phase of a Mars exploration mission (such as spacecraft, landers, habitats, or support infrastructure) that contributes specific functions toward achieving the mission’s overall objectives.
-
D.
series of robotic lunar probes
A series of robotic lunar probes is a coordinated set of unmanned spacecraft missions designed to explore, study, and collect data from the Moon’s surface, subsurface, and environment.
-
E.
spacecraft program
chosen
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.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.