Triple

T10976010
Position Surface form Disambiguated ID Type / Status
Subject Lee Navigation E259370 entity
Predicate hasLock P2431 FINISHED
Object Hertford Lock E260364 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: Hertford Lock | Statement: [Lee Navigation, hasLock, Hertford Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Hertford Lock
Context triple: [Lee Navigation, hasLock, Hertford Lock]
  • A. Hertford Lock chosen
    Hertford Lock is a navigation lock on the River Lea in Hertfordshire, England, used to manage water levels and enable boat passage along the waterway.
  • B. Eastham Lock
    Eastham Lock is a major lock complex at the entrance of the Manchester Ship Canal near the River Mersey, enabling sea-going vessels to access the inland waterway.
  • C. Saltersford Lock
    Saltersford Lock is a navigation lock on the River Weaver in Cheshire, England, used to manage water levels and enable boat passage along the river.
  • D. Sandford Lock
    Sandford Lock is a navigation lock on the River Chelmer in Essex, England, used to manage water levels and enable boat passage along the river.
  • E. Catteshall Lock
    Catteshall Lock is a historic navigation lock on the River Wey in Surrey, England, forming part of one of the country’s earliest commercial waterways.
  • 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_69d771f4e888819097433271a2f45ff3 completed April 9, 2026, 9:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69e2d7bcea448190b09906c79de67496 completed April 18, 2026, 1 a.m.
Created at: April 8, 2026, 9:24 p.m.