Triple

T9301497
Position Surface form Disambiguated ID Type / Status
Subject Cleethorpes E223772 entity
Predicate railConnectionsTo P13914 FINISHED
Object Barton-on-Humber E223774 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: Barton-on-Humber | Statement: [Cleethorpes, railConnectionsTo, Barton-on-Humber]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barton-on-Humber
Context triple: [Cleethorpes, railConnectionsTo, Barton-on-Humber]
  • A. Barton-on-Humber chosen
    Barton-on-Humber is a small historic town in North Lincolnshire, England, situated on the south bank of the Humber Estuary.
  • B. Sowerby Bridge
    Sowerby Bridge is a market town in Calderdale, West Yorkshire, England, known for its industrial heritage, canal and railway junctions, and position in the Upper Calder Valley.
  • C. Mirfield
    Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
  • D. Bridlington
    Bridlington is a coastal town and popular seaside resort on the North Sea in the East Riding of Yorkshire, England.
  • E. Bridlington
    Bridlington is the later name of the historical settlement originally known as Burlington in the former Province of New Jersey.
  • 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_69ca8423edb08190bc0c91287a484768 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd08d1d954819098be177addafa406 completed April 1, 2026, noon
NED1 Entity disambiguation (via context triple) batch_69d0b26302608190a59f3ed0694ce6d9 completed April 4, 2026, 6:40 a.m.
Created at: March 30, 2026, 7:36 p.m.