Triple

T23383193
Position Surface form Disambiguated ID Type / Status
Subject Woldingham railway station E593806 entity
Predicate locatedIn P40 FINISHED
Object Woldingham 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: Woldingham | Statement: [Woldingham railway station, locatedIn, Woldingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Woldingham
Context triple: [Woldingham railway station, locatedIn, Woldingham]
  • A. Woldingham chosen
    Woldingham is a rural village and civil parish in Surrey, England, known for its affluent residential character and location on the North Downs.
  • B. Warlingham
    Warlingham is a village and civil parish in Surrey, England, situated on the North Downs and functioning largely as a commuter settlement for London.
  • C. Sellindge
    Sellindge is a rural village in Kent, England, situated between Ashford and Folkestone and known for its community amenities and surrounding countryside.
  • D. Earlswood
    Earlswood is a residential suburb and locality in Surrey, England, situated just south of the town of Redhill.
  • E. Speldhurst
    Speldhurst is a rural village and civil parish in Kent, England, known for its historic church, traditional pubs, and scenic countryside near Royal Tunbridge Wells.
  • 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_69e25d268a50819095f2fd479da8ef3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a3b9287481908fd86c41f6d9fc53 completed April 29, 2026, 6:22 a.m.
Created at: April 17, 2026, 5:34 p.m.