Triple
T21584847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Miami River Canal |
E532620
|
entity |
| Predicate | connectedToNetwork |
P33235
|
FINISHED |
| Object | Ohio canal 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: Ohio canal system | Statement: [Great Miami River Canal, connectedToNetwork, Ohio canal system]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ohio canal system Context triple: [Great Miami River Canal, connectedToNetwork, Ohio canal system]
-
A.
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.
-
B.
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.
-
C.
Wabash and Erie Canal
The Wabash and Erie Canal was a 19th-century man-made waterway that connected the Great Lakes to the Ohio River, facilitating transportation and commerce across the Midwest.
-
D.
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.
-
E.
Miami and Erie Canal
The Miami and Erie Canal was a 19th-century man-made waterway in Ohio that linked the Ohio River to Lake Erie, playing a key role in regional transportation and commerce before the rise of railroads.
- 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: Ohio canal system Target entity description: The Ohio canal system was a 19th-century network of man-made waterways that facilitated transportation and commerce across Ohio by linking its major rivers, cities, and markets.
-
A.
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.
-
B.
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.
-
C.
Wabash and Erie Canal
The Wabash and Erie Canal was a 19th-century man-made waterway that connected the Great Lakes to the Ohio River, facilitating transportation and commerce across the Midwest.
-
D.
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.
-
E.
Miami and Erie Canal
The Miami and Erie Canal was a 19th-century man-made waterway in Ohio that linked the Ohio River to Lake Erie, playing a key role in regional transportation and commerce before the rise of railroads.
- F. None of above. chosen
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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5f2cc0819095552de70eb2ad8d |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 16, 2026, 6:31 p.m.