Triple
T10377946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CORS network |
E244554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | continuously operating reference station system |
C9448
|
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: continuously operating reference station system Context triple: [CORS network, instanceOf, continuously operating reference station system]
-
A.
GNSS reference network
chosen
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.
satellite-based augmentation system
A satellite-based augmentation system is an overlay to global navigation satellite systems that uses additional satellites and ground stations to provide improved accuracy, integrity, and availability for positioning and navigation services.
-
C.
regional navigation satellite system
A regional navigation satellite system is a space-based infrastructure that provides positioning, navigation, and timing services over a specific geographic region rather than globally.
-
D.
Global Navigation Satellite System
A Global Navigation Satellite System is a satellite-based infrastructure that provides continuous, worldwide positioning, navigation, and timing services to receivers on or near Earth’s surface.
-
E.
high-precision positioning technique
A high-precision positioning technique is a method or system that determines the exact location of an object or point with very fine spatial accuracy, often at the centimeter or millimeter level.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:03 p.m.