Triple

T16580875
Position Surface form Disambiguated ID Type / Status
Subject Hykeham railway station E402826 entity
Predicate serves P98 FINISHED
Object North Hykeham E402826 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: North Hykeham | Statement: [Hykeham railway station, serves, North Hykeham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: North Hykeham
Context triple: [Hykeham railway station, serves, North Hykeham]
  • A. North Hykeham chosen
    North Hykeham is a town in Lincolnshire, England, situated just southwest of the city of Lincoln and forming part of its suburban area.
  • B. Reedham
    Reedham is a riverside village in Norfolk, England, known for its historic ferry crossing and railway swing bridge over the River Yare.
  • C. Fareham
    Fareham is a market town in southern England situated between the cities of Southampton and Portsmouth.
  • D. Waterlooville
    Waterlooville is a town in Hampshire, England, situated north of Portsmouth and known primarily as a residential and commuter area.
  • E. Brinnington
    Brinnington is a residential suburb in the Metropolitan Borough of Stockport, Greater Manchester, England, known for its large housing estates and proximity to the River Tame.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35960834c819080eed0c9f32b881d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006ef0bc4c8190b06b03c06d344abf completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.