Triple
T15907878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope servicing mission |
E385768
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NASA spaceflight program element |
C33184
|
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 spaceflight program element Context triple: [Hubble Space Telescope servicing mission, instanceOf, NASA spaceflight program element]
-
A.
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.
-
B.
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.
-
C.
NASA program component
chosen
A NASA program component is a distinct organizational, technical, or operational element within a broader NASA program that contributes specific capabilities, resources, or functions toward achieving the program’s mission objectives.
-
D.
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.
-
E.
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.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.