Triple

T3523261
Position Surface form Disambiguated ID Type / Status
Subject Gomshall E74475 entity
Predicate locatedWestOf P4239 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: [Gomshall, locatedWestOf, Dorking]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dorking
Context triple: [Gomshall, locatedWestOf, 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. Burgess Hill
    Burgess Hill is a town in southeastern England known as a commuter hub with residential areas and light industry, situated within the county of West Sussex.
  • E. Esher
    Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to 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_69ad85d0c5488190a3d8e02ebd01a1aa completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc4f16b8819094ad2755670ddc7b completed March 8, 2026, 6:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69b54c2144708190a4a620222eeee5d3 completed March 14, 2026, 11:53 a.m.
Created at: March 8, 2026, 3:19 p.m.