Triple
T19511903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Marys Falls Canal |
E488176
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Soo Locks |
E169628
|
NE 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: Soo Locks | Statement: [Saint Marys Falls Canal, hasPart, Soo Locks]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soo Locks Context triple: [Saint Marys Falls Canal, hasPart, Soo Locks]
-
A.
Soo Locks
chosen
The Soo Locks are a set of ship locks on the St. Marys River between Lake Superior and Lake Huron that enable vessels to bypass the river’s rapids and navigate the Great Lakes.
-
B.
Løveid Locks
Løveid Locks is a historic lock system in Norway that forms part of the Telemark Canal, enabling boats to navigate between different water levels along the route.
-
C.
Kjeldal Locks
Kjeldal Locks is a historic lock system on Norway’s Telemark Canal, enabling boats to navigate elevation changes along the waterway.
-
D.
Bosley Locks
Bosley Locks is a historic flight of canal locks in Cheshire, England, that raises the Macclesfield Canal up the side of the Bosley Cloud hill.
-
E.
Ballard Locks
Ballard Locks, officially known as the Hiram M. Chittenden Locks, is a major lock system in Seattle that manages boat traffic and water levels between the freshwater lakes and the saltwater Puget Sound.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359908fc8190bd05f26d4271d268 |
completed | April 20, 2026, 2:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0747235758819086d85c107b187b7e |
completed | May 15, 2026, 4:17 p.m. |
Created at: April 10, 2026, 1:40 p.m.