Triple

T22356670
Position Surface form Disambiguated ID Type / Status
Subject Ellesmere Canal E552669 entity
Predicate terminus P388 FINISHED
Object Ellesmere Port NE NERFINISHED

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: Ellesmere Port | Statement: [Ellesmere Canal, terminus, Ellesmere Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ellesmere Port
Context triple: [Ellesmere Canal, terminus, Ellesmere Port]
  • A. Ellesmere Port chosen
    Ellesmere Port is an industrial town and port in Cheshire, England, known for its docks on the Manchester Ship Canal and proximity to Liverpool.
  • B. Runcorn
    Runcorn is an industrial town in Cheshire, England, situated on the southern bank of the River Mersey and known for its chemical industry and transport links.
  • C. Birkenhead
    Birkenhead is a suburb of Adelaide in South Australia, known for its proximity to the Port River and maritime and industrial heritage.
  • D. Birkenhead
    Birkenhead is a residential suburb on Auckland’s North Shore in New Zealand, known for its bush-clad hills, harbour views, and village-style shopping area.
  • E. Birkenhead
    Birkenhead is a town in north west England, situated on the Wirral Peninsula across the River Mersey from Liverpool, known historically for its shipbuilding and docks.
  • 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_69e11e4a0ad08190a385b4d343cf6524 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157d08b148190a9a4e445e8579219 completed April 29, 2026, 12:58 a.m.
Created at: April 16, 2026, 8:44 p.m.