Triple

T14616672
Position Surface form Disambiguated ID Type / Status
Subject Chelsham E343103 entity
Predicate locatedNear P294 FINISHED
Object Warlingham 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: Warlingham | Statement: [Chelsham, locatedNear, Warlingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Warlingham
Context triple: [Chelsham, locatedNear, Warlingham]
  • A. Warlingham chosen
    Warlingham is a village and civil parish in Surrey, England, situated on the North Downs and functioning largely as a commuter settlement for London.
  • B. Woldingham
    Woldingham is a rural village and civil parish in Surrey, England, known for its affluent residential character and location on the North Downs.
  • C. Limpsfield
    Limpsfield is a historic village and civil parish in Surrey, England, known for its picturesque countryside and traditional English character.
  • D. Lamberhurst
    Lamberhurst is a rural village in Kent, England, known for its historic buildings, vineyards, and scenic countryside within the High Weald Area of Outstanding Natural Beauty.
  • E. Bletchingley
    Bletchingley is a historic village in Surrey, England, known for its medieval origins and picturesque rural setting.
  • 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_69d822dec68081908c2553145c4051dc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb46439b88190a4affcc7ccedab6b completed April 14, 2026, 9:40 p.m.
Created at: April 10, 2026, 1:25 a.m.