Triple
T29766619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBAS |
E753930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite-based navigation aid |
C2386
|
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-based navigation aid Context triple: [GBAS, instanceOf, satellite-based navigation aid]
-
A.
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.
-
B.
satellite navigation system feature
A satellite navigation system feature is a specific capability or function within a satellite-based positioning system that enhances how location, routing, tracking, or related spatial information is calculated, presented, or used.
-
C.
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.
-
D.
navigational aid
chosen
A navigational aid is a tool, device, or system that helps users determine their position and plan or follow a route from one location to another.
-
E.
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.
- 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.