Triple
T17245575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck 2013 results |
E418616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cosmological data release |
C18048
|
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: cosmological data release Context triple: [Planck 2013 results, instanceOf, cosmological data release]
-
A.
astronomical data set
chosen
An astronomical data set is a structured collection of observational or simulated measurements about celestial objects and phenomena, typically including positions, brightnesses, spectra, and related metadata gathered using astronomical instruments.
-
B.
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.
-
C.
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.
-
D.
cosmology experiment
A cosmology experiment is a scientific investigation designed to measure and analyze cosmic phenomena—such as the cosmic microwave background, large-scale structure, or dark energy—to test and refine models of the universe’s origin, composition, and evolution.
-
E.
cosmology paper
A cosmology paper is a scholarly article that presents theoretical models, observational analyses, or simulations to investigate the origin, structure, evolution, and large-scale properties of the universe.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:39 a.m.