Triple
T12378334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River industrial corridor |
E295681
|
entity |
| Predicate | usedWaterwayFor |
P44236
|
FINISHED |
| Object | shipping |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: shipping | Statement: [Hudson River industrial corridor, usedWaterwayFor, shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWaterwayFor Context triple: [Hudson River industrial corridor, usedWaterwayFor, shipping]
-
A.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
B.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
C.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
D.
waterbodyUsedFor
chosen
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
E.
hasNearbyWatersUsedBy
Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
- F. None of above.
Provenance (3 batches)
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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fb8d6c081909e8bbbd52c73f29c |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.