Triple

T12000604
Position Surface form Disambiguated ID Type / Status
Subject Otonabee River E285648 entity
Predicate hasDam P8736 FINISHED
Object Lock 19 dam E170247 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: Lock 19 dam | Statement: [Otonabee River, hasDam, Lock 19 dam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Lock 19 dam
Context triple: [Otonabee River, hasDam, Lock 19 dam]
  • A. Hungerford lock
    Hungerford Lock is a lock on the Kennet and Avon Canal near Hungerford in Berkshire, England, used to raise and lower boats between different water levels.
  • B. Dutton Locks
    Dutton Locks is a set of navigation locks on the River Weaver in Cheshire, England, used to manage water levels and enable boat passage along the river.
  • C. Hillmorton Locks
    Hillmorton Locks is a historic flight of canal locks near Rugby in Warwickshire, England, known as one of the busiest and most significant lock sites on the British canal network.
  • D. Burleigh Falls Lock chosen
    Burleigh Falls Lock is a canal lock on Ontario’s Trent–Severn Waterway, known for managing navigation and water levels near the scenic Burleigh Falls area.
  • E. Bell Weir Lock
    Bell Weir Lock is a lock on the River Thames in England, situated near Egham and used to manage river navigation and water levels.
  • 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_69d6ab44a77c8190a652f4b27164e4ef completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903c26d7881909b67a31d04882eb5 completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4729eb4a081909d93b3fc74509d86 completed May 1, 2026, 9:30 a.m.
Created at: April 8, 2026, 9:46 p.m.