Triple

T10976170
Position Surface form Disambiguated ID Type / Status
Subject Hackney Cut E259374 entity
Predicate hasLock P2431 FINISHED
Object Old Ford Lock E896970 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: Old Ford Lock | Statement: [Hackney Cut, hasLock, Old Ford Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Ford Lock
Context triple: [Hackney Cut, hasLock, Old Ford Lock]
  • A. Old Ford Lock chosen
    Old Ford Lock is a historic canal lock on the River Lee Navigation in East London, serving as part of the city's inland waterway network.
  • 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. Rosedale Lock
    Rosedale Lock is a navigational lock on Ontario’s Trent–Severn Waterway that helps boats transition between different water levels along the canal system.
  • D. Gladstone Lock
    Gladstone Lock is a major ship lock within the Port of Liverpool that enables large vessels to access the port’s dock system from the River Mersey.
  • E. Allington Lock
    Allington Lock is a key navigation and flood-control lock on the River Medway in Kent, England, marking the tidal limit of the river.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d771f5bef481909043656c571fda89 completed April 9, 2026, 9:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69e344b433c481909bf22bba1b8dc3bd completed April 18, 2026, 8:45 a.m.
Created at: April 8, 2026, 9:24 p.m.