Triple

T4350083
Position Surface form Disambiguated ID Type / Status
Subject River Ember E98001 entity
Predicate locatedNear P294 FINISHED
Object Esher E26463 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: Esher | Statement: [River Ember, locatedNear, Esher]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Esher
Context triple: [River Ember, locatedNear, Esher]
  • A. Esher chosen
    Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
  • B. Esher and Walton
    Esher and Walton is a UK parliamentary constituency in Surrey, represented in the House of Commons and known for being a traditionally affluent, Conservative-leaning seat.
  • C. Isleworth
    Isleworth is a suburban town in West London, England, known for hosting major media and broadcasting facilities.
  • D. Egham
    Egham is a town in the county of Surrey in southeast England, known for its proximity to Runnymede, where Magna Carta was sealed.
  • E. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • 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_69b3454965f881908c41190bb22f0e4b completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b351a840248190b88c8a7be9158d25 completed March 12, 2026, 11:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a548f8081909e347a1c7cd4e9fc completed March 28, 2026, 12:01 a.m.
Created at: March 12, 2026, 11:15 p.m.