Triple
T17297321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck 2018 results |
E419944
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Planck mission data release |
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: Planck mission data release Context triple: [Planck 2018 results, instanceOf, Planck mission data release]
-
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.
Hubble Space Telescope survey
A Hubble Space Telescope survey is a systematic observational program using the HST to image or spectroscopically study selected regions of the sky or specific classes of astronomical objects to address defined scientific questions.
-
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
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.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.