Triple
T33397240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barycentric Celestial Reference System |
E855203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical coordinate system |
C16117
|
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 coordinate system Context triple: [Barycentric Celestial Reference System, instanceOf, astronomical coordinate system]
-
A.
celestial coordinate system
chosen
A celestial coordinate system is a framework for specifying the positions of objects in the sky using angular measurements relative to defined reference planes and points, such as the celestial equator and poles.
-
B.
astrometric standard
An astrometric standard is a celestial object with precisely known position and motion used as a reference to calibrate and validate astrometric measurements.
-
C.
astronomical equation
An astronomical equation is a mathematical expression or formula used to describe, predict, or relate celestial phenomena such as planetary motion, stellar properties, or cosmological parameters.
-
D.
astronomical reference parameter
An astronomical reference parameter is a standardized value or constant used to define, calibrate, or relate measurements in astronomy, such as positions, motions, or physical properties of celestial objects, within a chosen reference frame or system.
-
E.
geodetic coordinate system
A geodetic coordinate system is a reference framework that specifies locations on or near the Earth's surface using latitude, longitude, and often height relative to a defined ellipsoidal model of the Earth.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.