Triple
T36379132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IERS data and product centres |
E895993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geodetic data centre |
C61120
|
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: geodetic data centre Context triple: [IERS data and product centres, instanceOf, geodetic data centre]
-
A.
geodetic organization
chosen
A geodetic organization is an entity responsible for measuring, monitoring, and managing the Earth's geometric shape, gravity field, and spatial reference systems to support mapping, navigation, and geospatial analysis.
-
B.
geodetic datum
A geodetic datum is a reference framework consisting of a defined origin, orientation, and scale used to precisely locate points on the Earth’s surface in terms of latitude, longitude, and elevation.
-
C.
geodetic reference point
A geodetic reference point is a precisely surveyed physical location on the Earth's surface used as a fixed coordinate reference for mapping, surveying, and geospatial measurements.
-
D.
geodetic datum component
A geodetic datum component is an individual element (such as an ellipsoid, reference frame, or coordinate system parameter) that contributes to defining the position, orientation, and scale of a geodetic datum used for spatial referencing on or near the Earth’s surface.
-
E.
geodetic observing system
A geodetic observing system is an integrated network of instruments, platforms, and data-processing facilities designed to measure and monitor the Earth's shape, gravity field, rotation, and surface deformation with high precision.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.