Triple

T11779161
Position Surface form Disambiguated ID Type / Status
Subject Ockley E280095 entity
Predicate nearestLargeTown P1982 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: [Ockley, nearestLargeTown, Dorking]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dorking
Context triple: [Ockley, nearestLargeTown, 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. Purley
    Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
  • D. Chertsey
    Chertsey is a historic town in southeast England, known for its medieval abbey heritage and location on the River Thames.
  • E. Beddington
    Beddington is a suburban area in South London known for its historic village core, green spaces, and proximity to Croydon and central 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_69d6ab01d2688190ad8ed6bda487eaa5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a5623f708190a18aea570577a3f6 completed April 10, 2026, 7:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f72654dc88819095bc1ce23dfee4df completed May 3, 2026, 10:41 a.m.
Created at: April 8, 2026, 9:42 p.m.