Triple
T33397044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Geodetic Observing System |
E855199
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global geodetic infrastructure framework |
C5801
|
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: global geodetic infrastructure framework Context triple: [Global Geodetic Observing System, instanceOf, global geodetic infrastructure framework]
-
A.
GNSS reference network
A GNSS reference network is a coordinated system of continuously operating GNSS stations that provide precise, stable positioning and timing references for surveying, navigation, and geospatial applications.
-
B.
global Earth observation framework
A global Earth observation framework is an integrated system of satellites, ground stations, data standards, and collaborative policies designed to collect, share, and analyze Earth-related data for monitoring and managing the planet’s environment and resources.
-
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 service organization
A geodetic service organization is an entity that plans, conducts, and manages geodetic measurements and analyses to provide accurate reference frames, positioning data, and related geospatial services.
-
E.
global reference frame
chosen
A global reference frame is a fixed, overarching coordinate system used to consistently define positions, orientations, and motions of objects throughout an entire modeled world or environment.
- 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.