Triple

T10976131
Position Surface form Disambiguated ID Type / Status
Subject Bow Locks E259373 entity
Predicate hasAlternativeName P39 FINISHED
Object Bow Lock E259373 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: Bow Lock | Statement: [Bow Locks, hasAlternativeName, Bow Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Bow Lock
Context triple: [Bow Locks, hasAlternativeName, Bow Lock]
  • A. Bow Locks chosen
    Bow Locks is a set of navigation locks on the River Lea in East London that control water levels and enable boat passage between the river and surrounding waterways.
  • B. Cuton Lock
    Cuton Lock is a canal lock on the River Chelmer in Essex, England, used to raise and lower boats along the Chelmer and Blackwater Navigation.
  • C. Ickles Lock
    Ickles Lock is a canal lock on the Sheffield and South Yorkshire Navigation in South Yorkshire, England, used to raise and lower boats between different water levels.
  • D. Jordans Lock
    Jordans Lock is a canal lock on the Sheffield and South Yorkshire Navigation waterway in South Yorkshire, England.
  • E. Poe Lock
    Poe Lock is one of the major ship locks at the Soo Locks complex in Sault Ste. Marie, Michigan, enabling large commercial vessels to transit between Lake Superior and the lower Great Lakes.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d771f5bef481909043656c571fda89 completed April 9, 2026, 9:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69e2d7bcea448190b09906c79de67496 completed April 18, 2026, 1 a.m.
Created at: April 8, 2026, 9:24 p.m.