Triple

T2309827
Position Surface form Disambiguated ID Type / Status
Subject Kingsway Tunnel E51926 entity
Predicate connects P390 FINISHED
Object Wallasey E70000 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: Wallasey | Statement: [Kingsway Tunnel, connects, Wallasey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wallasey
Context triple: [Kingsway Tunnel, connects, Wallasey]
  • A. Wallasey chosen
    Wallasey is a coastal town on the Wirral Peninsula in northwest England, situated at the mouth of the River Mersey opposite Liverpool.
  • B. Maghull
    Maghull is a suburban town in Merseyside, England, situated to the north of Liverpool and functioning largely as a residential commuter area.
  • C. Saltney
    Saltney is a town near the England–Wales border, close to Chester, known historically for its industrial activity and proximity to the River Dee.
  • D. Barrow-in-Furness
    Barrow-in-Furness is a coastal industrial town in Cumbria, England, historically known for its shipbuilding and submarine construction.
  • E. Ellesmere Port
    Ellesmere Port is an industrial town and port in Cheshire, England, known for its docks on the Manchester Ship Canal and proximity to Liverpool.
  • 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_69a88b0bb30c81908ded03b006d29387 completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc6098ce88190ba2e987e6f0737ac completed March 7, 2026, 6:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae7f3a007c8190b5c8683ced9d77fa completed March 9, 2026, 8:05 a.m.
Created at: March 4, 2026, 7:49 p.m.