Triple

T1163312
Position Surface form Disambiguated ID Type / Status
Subject Epsom E24540 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. Wantage
    Wantage is a historic market town in Oxfordshire, England, best known as the birthplace of King Alfred the Great.
  • C. Beaconsfield
    Beaconsfield is a suburban city on the western part of the Island of Montreal in Quebec, Canada, known for its residential character and waterfront along Lake Saint-Louis.
  • D. Isleworth
    Isleworth is a suburban town in West London, England, known for hosting major media and broadcasting facilities.
  • E. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcc9dc5081908e225a485186ab12 completed March 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69adeab57c8c81908b1dbdaf7ba4b29b completed March 8, 2026, 9:31 p.m.
Created at: March 1, 2026, 7:45 p.m.