Triple
T23737281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satellite-Based Augmentation Systems |
E586572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Navigation infrastructure |
C48004
|
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: Navigation infrastructure Context triple: [Satellite-Based Augmentation Systems, instanceOf, Navigation infrastructure]
-
A.
navigation infrastructure vicinity
Navigation infrastructure vicinity is the spatial region surrounding navigational aids or facilities (such as beacons, buoys, or control towers) within which their presence, signals, or operational constraints are relevant to route planning and movement.
-
B.
navigation system
A navigation system is a coordinated set of hardware and software components that determines a user's position and provides optimal routes and guidance to reach desired destinations.
-
C.
navigation improvement project
A navigation improvement project is an initiative focused on analyzing, redesigning, and optimizing wayfinding systems, routes, and interfaces to make it easier and more efficient for users to reach their desired destinations.
-
D.
navigational passage
A navigational passage is a corridor, channel, or route—often within a building, vessel, or geographic area—designed to guide movement safely and efficiently from one location to another.
-
E.
traffic and navigation app
A traffic and navigation app is a mobile or web-based application that provides real-time route guidance, traffic conditions, and travel time estimates to help users efficiently reach their destinations.
- F. None of above. chosen
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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:10 p.m.