Triple

T19477042
Position Surface form Disambiguated ID Type / Status
Subject The Commandery, Worcester E487271 entity
Predicate adjacentTo P224 FINISHED
Object Worcester and Birmingham Canal E940866 NE FINISHED

How this triple was built (1 step)

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.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Worcester and Birmingham Canal
Context triple: [The Commandery, Worcester, adjacentTo, Worcester and Birmingham Canal]
  • A. Worcester and Birmingham Canal chosen
    The Worcester and Birmingham Canal is an English inland waterway linking the city of Worcester to Birmingham, historically important for industrial transport and now popular for leisure boating.
  • B. Warwick and Birmingham Canal
    The Warwick and Birmingham Canal was a historic English waterway linking Birmingham to Warwick, later incorporated into the Grand Union Canal network.
  • C. Staffordshire and Worcestershire Canal
    The Staffordshire and Worcestershire Canal is an 18th-century English inland waterway that forms a key link between the River Severn and the Midlands canal network.
  • D. Birmingham and Fazeley Canal
    The Birmingham and Fazeley Canal is an 18th-century English narrow canal that forms part of the Birmingham Canal Navigations, linking Birmingham with Fazeley and connecting to wider Midlands waterways.
  • E. Birmingham Canal
    The Birmingham Canal is a historic waterway in England that formed the core of Birmingham’s industrial canal network, linking the city to major trade routes during the Industrial Revolution.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a074053f7b48190a726ef5e285ed62a completed May 15, 2026, 3:48 p.m.
Created at: April 10, 2026, 1:39 p.m.