Triple

T19293966
Position Surface form Disambiguated ID Type / Status
Subject Selhurst railway station E482511 entity
Predicate servedByServiceTo P6787 FINISHED
Object Sutton NE NERFINISHED

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: Sutton | Statement: [Selhurst railway station, servedByServiceTo, Sutton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sutton
Context triple: [Selhurst railway station, servedByServiceTo, Sutton]
  • A. Sutton
    Sutton is a village and civil parish located in the county of Suffolk in eastern England.
  • B. Sutton
    Sutton is a small rural village in New South Wales, Australia, located near Canberra and known for its quiet countryside setting.
  • C. Sutton
    Sutton is a small rural village located within the district of West Oxfordshire in England.
  • D. Sutton chosen
    Sutton is a large suburban town in South London, England, known as the principal settlement of the London Borough of Sutton.
  • E. Sutton
    Sutton is a small community within the town of Georgina in Ontario, Canada, known for its proximity to Lake Simcoe and its role as a local service and recreational hub.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8cf61b0819096fe3e4107827c4e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fc84500c81908ac53711335ad2d9 completed April 20, 2026, 10:14 a.m.
Created at: April 10, 2026, 1:31 p.m.