Triple
T6327380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Navigation Satellite System Infrastructure |
E141893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global positioning system |
C7161
|
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 positioning system Context triple: [Global Navigation Satellite System Infrastructure, instanceOf, global positioning system]
-
A.
Global Navigation Satellite System
chosen
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
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.
global communication system
A global communication system is an interconnected network of technologies, protocols, and infrastructures that enables real-time exchange of information across the world regardless of geographic location.
-
D.
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.
-
E.
global reference frame
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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.