Triple

T6865907
Position Surface form Disambiguated ID Type / Status
Subject Regent’s Canal E158399 entity
Predicate hasStructure P35 FINISHED
Object Camden Lock E176177 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: Camden Lock | Statement: [Regent’s Canal, hasStructure, Camden Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Camden Lock
Context triple: [Regent’s Canal, hasStructure, Camden Lock]
  • A. Camden Lock chosen
    Camden Lock is a historic canal lock and bustling market area in Camden Town, London, known for its alternative culture, shops, and street food.
  • B. Sunbury Lock
    Sunbury Lock is a lock on the River Thames in England, used to manage water levels and enable boats to navigate between different stretches of the river.
  • C. 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.
  • D. Loughborough Lock
    Loughborough Lock is a navigation lock on the River Soar in Loughborough, Leicestershire, helping boats pass between different water levels on the river.
  • E. Hertford Lock
    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.
  • 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_69c68831e3648190a643c328122e4d43 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d88c48f08190b9afba97b19d8605 completed March 27, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7428b2fe88190ac1798922e2b9620 completed March 28, 2026, 2:52 a.m.
Created at: March 27, 2026, 2:21 p.m.