Triple

T22211091
Position Surface form Disambiguated ID Type / Status
Subject Middlewich Branch E548946 entity
Predicate hasLock P2431 FINISHED
Object Cholmondeston Lock NE NERFINISHED

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: Cholmondeston Lock | Statement: [Middlewich Branch, hasLock, Cholmondeston Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cholmondeston Lock
Context triple: [Middlewich Branch, hasLock, Cholmondeston Lock]
  • A. 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.
  • B. 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.
  • C. Stanthorne Lock chosen
    Stanthorne Lock is a canal lock on the Middlewich Branch of the Shropshire Union Canal in Cheshire, England, used to raise and lower boats between different water levels.
  • D. Thurmaston Lock
    Thurmaston Lock is a navigation lock on the River Soar in Leicestershire, England, used to manage water levels and enable boat passage along the river.
  • E. Inglesham Lock
    Inglesham Lock is a historic lock on the Thames and Severn Canal in England, notable as one of the canal’s westernmost structures near the River Thames.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b2bcf748190a9721f0c9ae17e70 completed April 28, 2026, 9:48 p.m.
Created at: April 16, 2026, 8:36 p.m.