Triple
T29766618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBAS |
E753930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground-based augmentation system |
C28613
|
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: ground-based augmentation system Context triple: [GBAS, instanceOf, ground-based augmentation system]
-
A.
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.
-
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.
satellite navigation infrastructure component
A satellite navigation infrastructure component is a physical or logical element—such as satellites, ground stations, control systems, or communication links—that collectively enables the generation, transmission, correction, and reception of positioning, navigation, and timing signals.
-
D.
terrestrial navigation system
chosen
A terrestrial navigation system is a ground-based infrastructure and associated equipment that determine a vehicle’s position, velocity, and course using signals or references located on or near the Earth’s surface.
-
E.
GNSS service organization
An organization that plans, operates, maintains, and manages Global Navigation Satellite System (GNSS) infrastructure and services to provide reliable positioning, navigation, and timing information to users.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:38 p.m.