Triple

T10976001
Position Surface form Disambiguated ID Type / Status
Subject Lee Navigation E259370 entity
Predicate terminus P388 FINISHED
Object Limehouse Basin E626661 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: Limehouse Basin | Statement: [Lee Navigation, terminus, Limehouse Basin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Limehouse Basin
Context triple: [Lee Navigation, terminus, Limehouse Basin]
  • A. Limehouse Basin chosen
    Limehouse Basin is a marina and former dock in East London that serves as the junction between the Regent’s Canal and the River Thames.
  • B. Shadwell Basin
    Shadwell Basin is a former dock in East London that has been transformed into a residential and leisure area centered around a large body of water used for recreation and watersports.
  • C. Paddington Basin
    Paddington Basin is a redeveloped canal-side area in central London featuring modern offices, apartments, and waterside public spaces.
  • D. Wapping Dock
    Wapping Dock is a historic dock complex on the River Mersey in Liverpool, England, known for its 19th-century brick warehouses and role in the city’s maritime trade.
  • E. Limehouse Cut
    Limehouse Cut is a historic canal in East London that links the River Lea to the River Thames, forming part of the city’s inland waterway network.
  • 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_69d771f4e888819097433271a2f45ff3 completed April 9, 2026, 9:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69e344b433c481909bf22bba1b8dc3bd completed April 18, 2026, 8:45 a.m.
Created at: April 8, 2026, 9:24 p.m.