Triple
T19170220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie Canal Lock E-4 |
E469299
|
entity |
| Predicate | waterwayDirectionServed |
P75396
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Erie Canal Lock E-4, waterwayDirectionServed, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayDirectionServed Context triple: [Erie Canal Lock E-4, waterwayDirectionServed, east–west]
-
A.
waterwayDirection
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
waterwayDestination
Indicates that a waterway leads to, flows into, or terminates at a specified destination.
-
D.
waterwayLinkBetween
Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
-
E.
waterwayAccess
Indicates that one location has direct access to a waterway (such as a river, canal, or sea route) that can be used for transport, navigation, or related activities.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f163c5888190b4880471d17b4f51 |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.