Triple

T23528901
Position Surface form Disambiguated ID Type / Status
Subject Epsom to London Victoria route E576507 entity
Predicate connects P390 FINISHED
Object Epsom 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: Epsom | Statement: [Epsom to London Victoria route, connects, Epsom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Epsom
Context triple: [Epsom to London Victoria route, connects, Epsom]
  • A. Epsom
    Epsom is a small unincorporated rural community located in Vance County, North Carolina.
  • B. Epsom chosen
    Epsom is a market town in Surrey, England, best known for the Epsom Downs Racecourse and the famous Epsom Derby horse race.
  • C. Epsom
    Epsom is a residential suburb in central Auckland, New Zealand, known for its leafy streets, historic villas, and proximity to top schools and Cornwall Park.
  • D. Epsom Wells
    Epsom Wells is a Restoration-era comedy play by Thomas Shadwell, best known for its satirical portrayal of fashionable spa society in 17th-century England.
  • E. Yate
    Yate is a town in South Gloucestershire, England, known as a residential and commercial centre north of Bristol.
  • 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ac758038819098f5f597be39274e completed April 29, 2026, 7 a.m.
Created at: April 17, 2026, 6:09 p.m.