Triple

T1219573
Position Surface form Disambiguated ID Type / Status
Subject River Wey E26186 entity
Predicate hasLock P2431 FINISHED
Object Millmead Lock E144421 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: Millmead Lock | Statement: [River Wey, hasLock, Millmead Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Millmead Lock
Context triple: [River Wey, hasLock, Millmead Lock]
  • A. 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.
  • B. Kirkstead Lock
    Kirkstead Lock is a navigation lock on the River Witham in Lincolnshire, England, used to manage water levels and enable boat passage along the river.
  • C. Barton Lock
    Barton Lock is a lock on the Manchester Ship Canal that enables vessels to navigate changes in water level along this major industrial waterway in northwest England.
  • D. Stoke Lock chosen
    Stoke Lock is a navigation lock on the River Wey in Surrey, England, used to manage water levels and enable boat passage along the waterway.
  • E. Bardney Lock
    Bardney Lock is a navigation lock on the River Witham in Lincolnshire, England, used to manage water levels and enable boat passage along 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_69a4948331fc8190b531ac9bec71c491 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be1d55a08190a138b2411a7c4376 completed March 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69aca2eb158081909f1175d8f4daaa96 completed March 7, 2026, 10:12 p.m.
Created at: March 1, 2026, 7:46 p.m.