Triple
T6327692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Real-time Kinematic Positioning |
E141899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite navigation technique |
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: satellite navigation technique Context triple: [Real-time Kinematic Positioning, instanceOf, satellite navigation technique]
-
A.
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.
-
B.
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.
-
C.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
D.
satellite program
A satellite program is an organized initiative that designs, builds, launches, and operates satellites to achieve specific objectives such as communication, Earth observation, navigation, or scientific research.
-
E.
geostationary communications satellite
A geostationary communications satellite is a spacecraft positioned in an equatorial orbit that matches Earth's rotation, remaining fixed over one longitude to relay telecommunications signals between ground stations.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.