Triple
T36379133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IERS data and product centres |
E895993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical data centre |
C64234
|
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 centre Context triple: [IERS data and product centres, instanceOf, astronomical data centre]
-
A.
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.
-
B.
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.
-
C.
astronomical research institute
An astronomical research institute is an organization dedicated to the systematic study of celestial objects and phenomena through observation, theory, and instrumentation development.
-
D.
astronomical data analysis software
Astronomical data analysis software is a specialized toolset that ingests, processes, and interprets observational data from telescopes and space missions to extract, visualize, and quantify astrophysical information.
-
E.
astronomical observatory
An astronomical observatory is a facility equipped with specialized instruments and structures designed to observe, record, and analyze celestial objects and phenomena.
- F. None of above. chosen
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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.