Triple
T16431348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Distributed Active Archive Centers |
E399076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of EOSDIS |
C32733
|
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: component of EOSDIS Context triple: [NASA Distributed Active Archive Centers, instanceOf, component of EOSDIS]
-
A.
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.
-
B.
space mission data archive
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.
-
C.
NASA program infrastructure
chosen
NASA program infrastructure encompasses the organizational structures, facilities, technologies, processes, and support systems that enable the planning, execution, and management of NASA’s missions and research programs.
-
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.
NASA field center precursor
A NASA field center precursor is an early organizational entity, facility, or program that laid the technical, institutional, or infrastructural groundwork for the later establishment of a formal NASA field center.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.