Triple
T16431346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Distributed Active Archive Centers |
E399076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data archive center network |
C33945
|
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: data archive center network Context triple: [NASA Distributed Active Archive Centers, instanceOf, data archive center network]
-
A.
scientific data archive
A scientific data archive is a structured repository that securely stores, preserves, and provides organized access to research data and associated metadata for long-term reuse and verification.
-
B.
archival institution network
chosen
An archival institution network is a coordinated system of archives and related organizations that collaborate to preserve, manage, and provide access to documentary heritage across multiple institutions.
-
C.
astronomical data archive
An astronomical data archive is a curated repository that stores, organizes, and provides access to observational and simulated data from astronomical instruments and surveys for scientific analysis and long-term preservation.
-
D.
astronomical data archive
An astronomical data archive is a curated, long-term repository that stores, organizes, and provides access to observational and simulated data from astronomical instruments and surveys for scientific analysis and reuse.
-
E.
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.
- 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.