Triple
T17426814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Planetary Data System |
E423758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planetary science data system |
C35890
|
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: planetary science data system Context triple: [NASA Planetary Data System, instanceOf, planetary science data system]
-
A.
planetary science program office
A planetary science program office is an organizational unit that plans, coordinates, and manages scientific missions, research activities, and resources focused on the study of planets, moons, and other bodies in the solar system and beyond.
-
B.
planetary science mission element
A planetary science mission element is a distinct component or subsystem of a space mission—such as an instrument, spacecraft module, or operational capability—designed to enable the collection, transmission, or analysis of scientific data about planets and other solar system bodies.
-
C.
NASA mission data product
A NASA mission data product is a curated, standardized dataset or information package derived from raw mission observations, processed and documented to support scientific analysis, archiving, and public dissemination.
-
D.
space mission data archive
chosen
A space mission data archive is a centralized, long-term repository that stores, organizes, preserves, and provides access to all scientific and engineering data products generated by space missions.
-
E.
planetary scientist
A planetary scientist is a researcher who studies planets, moons, and other celestial bodies to understand their composition, formation, evolution, and potential to support life.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:46 a.m.