Triple
T10674018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McClellan–Kerr Arkansas River Navigation System |
E251566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigation system |
C28834
|
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 system Context triple: [McClellan–Kerr Arkansas River Navigation System, instanceOf, navigation system]
-
A.
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.
-
B.
navigator
A navigator is an entity responsible for determining and directing the optimal path or course from a starting point to a desired destination using available information and tools.
-
C.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
D.
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.
-
E.
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.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.