Triple

T11780026
Position Surface form Disambiguated ID Type / Status
Subject Boulter’s Lock E280117 entity
Predicate locatedUpstreamOf P5955 FINISHED
Object Bray Lock E946203 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: Bray Lock | Statement: [Boulter’s Lock, locatedUpstreamOf, Bray Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bray Lock
Context triple: [Boulter’s Lock, locatedUpstreamOf, Bray Lock]
  • A. Bray Lock chosen
    Bray Lock is a Thames River lock and weir near the village of Bray in Berkshire, England, used for managing river navigation and water levels.
  • B. Jordans Lock
    Jordans Lock is a canal lock on the Sheffield and South Yorkshire Navigation waterway in South Yorkshire, England.
  • C. 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.
  • D. Bray Harbour
    Bray Harbour is a small coastal marina and fishing port serving the seaside town of Bray in County Wicklow, Ireland.
  • E. Tinsley Locks
    Tinsley Locks is a flight of canal locks near Sheffield, England, that raises the Sheffield and South Yorkshire Navigation from the River Don up to the city’s canal basin.
  • 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_69d6ab01d2688190ad8ed6bda487eaa5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a5623f708190a18aea570577a3f6 completed April 10, 2026, 7:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f130cb31f48190a9357cce47a7b192 completed April 28, 2026, 10:12 p.m.
Created at: April 8, 2026, 9:42 p.m.