Triple
T6327379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Navigation Satellite System Infrastructure |
E141893
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigation infrastructure |
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: navigation infrastructure Context triple: [Global Navigation Satellite System Infrastructure, 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.
transport infrastructure network
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
C.
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.
-
D.
road infrastructure
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
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.
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.