Triple

T941762
Position Surface form Disambiguated ID Type / Status
Subject Cherkley Court E20321 entity
Predicate locatedNear P294 FINISHED
Object Dorking E26185 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: Dorking | Statement: [Cherkley Court, locatedNear, Dorking]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dorking
Context triple: [Cherkley Court, locatedNear, Dorking]
  • A. Dorking chosen
    Dorking is a historic market town in southeast England, known for its scenic setting in the Surrey Hills and its traditional high street, vineyards, and surrounding countryside.
  • B. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • C. Chertsey
    Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
  • D. Esher
    Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
  • E. Farnham
    Farnham is a historic market town in southern England known for its Georgian streets, medieval castle, and surrounding Surrey countryside.
  • 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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3a1a4888190997adf56eb761431 completed March 1, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad293209648190a380175f85d6efcc completed March 8, 2026, 7:45 a.m.
Created at: March 1, 2026, 7:40 p.m.