Triple
T35506406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AllWISE Explanatory Supplement |
E1026161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical data guide |
C17300
|
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: astronomical data guide Context triple: [AllWISE Explanatory Supplement, instanceOf, astronomical data guide]
-
A.
astronomical data set
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.
astronomical catalogue
chosen
An astronomical catalogue is a systematically organized list of celestial objects, typically including their positions, brightness, and other observational properties for scientific reference and study.
-
E.
astronomical service
An astronomical service is a system or organization that provides access to astronomical data, observations, analysis tools, or related support to users such as researchers, educators, or the public.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.