Triple
T36847954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Jet Propulsion Laboratory programs |
E910602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space exploration program portfolio |
C65910
|
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: space exploration program portfolio Context triple: [NASA Jet Propulsion Laboratory programs, instanceOf, space exploration program portfolio]
-
A.
space exploration programme
A space exploration programme is an organized, long-term initiative that plans, funds, and conducts missions and research activities to explore outer space and expand scientific and technological knowledge.
-
B.
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.
-
C.
planetary exploration program
A planetary exploration program is an organized, long-term initiative that plans, funds, and conducts missions to study other planets and celestial bodies using robotic or crewed spacecraft.
-
D.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
E.
space science programme
A space science programme is an organized set of research, missions, and educational activities focused on exploring and understanding space, celestial bodies, and related physical phenomena.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.