Triple
T19800038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erie Canal Lock E-6 |
E475647
|
entity |
| Predicate | navigationSystem |
P8170
|
FINISHED |
| Object | Erie Canal navigation system |
—
|
NE NERFINISHED |
How this triple was built (3 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: Erie Canal navigation system | Statement: [Erie Canal Lock E-6, navigationSystem, Erie Canal navigation system]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Erie Canal navigation system Context triple: [Erie Canal Lock E-6, navigationSystem, Erie Canal navigation system]
-
A.
New York State Canal System
The New York State Canal System is a network of interconnected canals and waterways in New York that evolved from historic routes like the Erie Canal and now supports recreation, tourism, and limited commercial navigation.
-
B.
Ohio and Erie Canal
The Ohio and Erie Canal was a 19th-century waterway in Ohio that linked Lake Erie to the Ohio River, spurring economic growth and the development of cities such as Akron.
-
C.
St. Lawrence canals system
The St. Lawrence canals system was a network of navigation canals built along the St. Lawrence River to bypass rapids and facilitate commercial shipping between the Great Lakes and the Atlantic Ocean.
-
D.
Oswego Canal lock system
The Oswego Canal lock system is a series of navigation locks in New York State that enable vessels to travel between the Erie Canal and Lake Ontario by managing changes in water elevation.
-
E.
Holyoke Canal System
The Holyoke Canal System is a historic network of industrial power canals in Holyoke, Massachusetts, built in the 19th century to harness the Connecticut River for manufacturing and mill operations.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Erie Canal navigation system Target entity description: The Erie Canal navigation system is the integrated network of locks, channels, and control structures that manages vessel movement and water levels along New York State’s historic Erie Canal.
-
A.
New York State Canal System
chosen
The New York State Canal System is a network of interconnected canals and waterways in New York that evolved from historic routes like the Erie Canal and now supports recreation, tourism, and limited commercial navigation.
-
B.
Ohio and Erie Canal
The Ohio and Erie Canal was a 19th-century waterway in Ohio that linked Lake Erie to the Ohio River, spurring economic growth and the development of cities such as Akron.
-
C.
St. Lawrence canals system
The St. Lawrence canals system was a network of navigation canals built along the St. Lawrence River to bypass rapids and facilitate commercial shipping between the Great Lakes and the Atlantic Ocean.
-
D.
Oswego Canal lock system
The Oswego Canal lock system is a series of navigation locks in New York State that enable vessels to travel between the Erie Canal and Lake Ontario by managing changes in water elevation.
-
E.
Holyoke Canal System
The Holyoke Canal System is a historic network of industrial power canals in Holyoke, Massachusetts, built in the 19th century to harness the Connecticut River for manufacturing and mill operations.
- F. None of above.
Provenance (2 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653cb865c81909696d2b37476f62f |
completed | April 20, 2026, 4:26 p.m. |
Created at: April 10, 2026, 1:49 p.m.