Triple

T21000576
Position Surface form Disambiguated ID Type / Status
Subject Wonersh E517274 entity
Predicate locatedNear P294 FINISHED
Object Cranleigh NE NERFINISHED

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: Cranleigh | Statement: [Wonersh, locatedNear, Cranleigh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cranleigh
Context triple: [Wonersh, locatedNear, Cranleigh]
  • A. Cranleigh chosen
    Cranleigh is a large village and civil parish in the county of Surrey in southeast England, known for its rural setting and local amenities.
  • B. Cranleigh Waters
    Cranleigh Waters is a small river in Surrey, England, that flows through the village of Cranleigh and joins the River Wey.
  • C. Adcote
    Adcote is a Victorian country house in Shropshire, England, designed in the late 19th century by architect Richard Norman Shaw in a distinctive Tudor Revival style.
  • D. Bryanston
    Bryanston is an affluent residential and commercial suburb located within the Sandton area of Johannesburg, South Africa.
  • E. Shepherdswell
    Shepherdswell is a village in Kent, England, situated in the Dover district and known for its rural setting and historic parish church.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc24a6dc8190a6bf81cf1d9590c0 completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:52 p.m.