Triple

T18341617
Position Surface form Disambiguated ID Type / Status
Subject Epsom E439416 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Ashtead E77658 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: Ashtead | Statement: [Epsom, hasNearbySettlement, Ashtead]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashtead
Context triple: [Epsom, hasNearbySettlement, Ashtead]
  • A. Ashtead chosen
    Ashtead is a large suburban village in Surrey, England, known for its residential character, local amenities, and proximity to the town of Leatherhead.
  • B. Orsett
    Orsett is a village and civil parish in the borough of Thurrock in Essex, England, known for its historic church and traditional village green.
  • C. Hamstead
    Hamstead is a suburban residential area in the West Midlands, England, situated between Birmingham and Sandwell.
  • D. Wheathampstead
    Wheathampstead is a historic village and civil parish in Hertfordshire, England, known for its rural character and ancient archaeological sites.
  • E. Twyford
    Twyford is a village and civil parish in Berkshire, England, known as a commuter settlement between Reading and London.
  • 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_69d8b9175fec8190af865699b4e64d8c completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e514f0b5a881908056d48bc48124b8 completed April 19, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a07470390208190be9956c308a7e194 completed May 15, 2026, 4:17 p.m.
Created at: April 10, 2026, 10:37 a.m.