Triple
T18054220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbor Deepening Project of the Port of New York and New Jersey |
E431995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigation improvement project |
C39769
|
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 improvement project Context triple: [Harbor Deepening Project of the Port of New York and New Jersey, instanceOf, navigation improvement project]
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
road endpoint
A road endpoint is a location where a road segment terminates, either by connecting to another road, transitioning into a different type of pathway, or ending without continuation.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.