Triple

T15811909
Position Surface form Disambiguated ID Type / Status
Subject Worle railway station E383374 entity
Predicate serves P98 FINISHED
Object Worle E1177840 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: Worle | Statement: [Worle railway station, serves, Worle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Worle
Context triple: [Worle railway station, serves, Worle]
  • A. Worle chosen
    Worle is a suburban area near Weston-super-Mare in North Somerset, England, known primarily as a residential community with rail links to surrounding regions.
  • B. Worstead
    Worstead is a small rural village and railway stop in Norfolk, England, situated on the Bittern Line between Norwich and the North Norfolk coast.
  • C. Southwold
    Southwold is a small seaside town and popular tourist resort on the North Sea coast of Suffolk, England, known for its pier, beach huts, and historic lighthouse.
  • D. Southwold
    Southwold is a residential neighbourhood within the town of Bicester in Oxfordshire, England.
  • E. Shevington
    Shevington is a village and civil parish in the Metropolitan Borough of Wigan, Greater Manchester, England.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b52bbb888190b226567e84ced7e9 completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffa131784c8190bd6aba2cca084d20 completed May 9, 2026, 9:03 p.m.
Created at: April 10, 2026, 4:49 a.m.