Triple

T10682963
Position Surface form Disambiguated ID Type / Status
Subject Worksop railway station E251801 entity
Predicate hasServiceTo P6787 FINISHED
Object Retford E149932 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: Retford | Statement: [Worksop railway station, hasServiceTo, Retford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Retford
Context triple: [Worksop railway station, hasServiceTo, Retford]
  • A. Retford chosen
    Retford is a historic market town in the English county of Nottinghamshire, known for its traditional town center and transport links.
  • B. Newark-on-Trent
    Newark-on-Trent is a historic market town in Nottinghamshire, England, known for its medieval castle ruins, role in the English Civil War, and position on the River Trent.
  • C. Yorkton
    Yorkton is a small city in southeastern Saskatchewan, Canada, known as a regional hub for agriculture and services.
  • D. Rochford
    Rochford is a small town in Essex, England, serving as the administrative center for the surrounding Rochford District.
  • E. Morpeth
    Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fcc43b9481908f35490db93db76c completed April 9, 2026, 1:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d998c6fb4881908a8e13912c405ec8 completed April 11, 2026, 12:41 a.m.
Created at: April 8, 2026, 9:10 p.m.