Triple

T1319811
Position Surface form Disambiguated ID Type / Status
Subject Locomotion E28190 entity
Predicate location P40 FINISHED
Object Shildon E151214 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: Shildon | Statement: [Locomotion, location, Shildon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shildon
Context triple: [Locomotion, location, Shildon]
  • A. Shildon chosen
    Shildon is a town in County Durham, England, historically significant as a cradle of the railway industry and home to major railway heritage attractions.
  • B. South Shields
    South Shields is a coastal town in Tyne and Wear, England, known historically for its shipbuilding and as part of the Tyneside urban area.
  • C. Retford
    Retford is a historic market town in the English county of Nottinghamshire, known for its traditional town center and transport links.
  • D. Shirebrook
    Shirebrook is a former mining town in the Bolsover district of Derbyshire, England, known for its coal mining heritage and later redevelopment around a major distribution centre.
  • E. Milnrow
    Milnrow is a town in Greater Manchester, England, historically part of Lancashire and known for its textile heritage and proximity to the Pennine hills.
  • 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_69a498532c3481909223b74af2e578df completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c179883c8190b68fbeebb9696982 completed March 1, 2026, 10:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69acc6255b808190823bc240365ed304 completed March 8, 2026, 12:43 a.m.
Created at: March 1, 2026, 7:55 p.m.