Triple

T5249013
Position Surface form Disambiguated ID Type / Status
Subject A240 road E118534 entity
Predicate connects P390 FINISHED
Object Epsom E24540 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: Epsom | Statement: [A240 road, connects, Epsom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Epsom
Context triple: [A240 road, connects, Epsom]
  • A. Epsom chosen
    Epsom is a market town in Surrey, England, best known for the Epsom Downs Racecourse and the famous Epsom Derby horse race.
  • B. Yate
    Yate is a town in South Gloucestershire, England, known as a residential and commercial centre north of Bristol.
  • C. Leamington Spa
    Leamington Spa is a historic spa town in Warwickshire, England, known for its Regency architecture, landscaped parks, and former popularity as a fashionable health resort.
  • D. Farnham
    Farnham is a historic market town in southern England known for its Georgian streets, medieval castle, and surrounding Surrey countryside.
  • E. Maidenhead
    Maidenhead is a large riverside town on the River Thames in Berkshire, England, known as a commuter hub for London with a mix of historic and modern development.
  • 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_69bd4468aacc8190a8196f71855cdf4f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b787b34819081af96de9355bb4f completed March 20, 2026, 4:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef83998f881909fef2746f5c496af completed March 21, 2026, 7:57 p.m.
Created at: March 20, 2026, 1:50 p.m.