Triple

T4349881
Position Surface form Disambiguated ID Type / Status
Subject Hooley E97996 entity
Predicate locatedNear P294 FINISHED
Object Coulsdon E208722 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: Coulsdon | Statement: [Hooley, locatedNear, Coulsdon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Coulsdon
Context triple: [Hooley, locatedNear, Coulsdon]
  • A. Coulsdon chosen
    Coulsdon is a suburban town in the London Borough of Croydon, England, known for its residential character and proximity to the North Downs.
  • B. 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.
  • C. Weybridge
    Weybridge is a suburban town in southeast England known for its affluent residential areas and proximity to the River Thames and major transport links into London.
  • D. 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.
  • E. Surbiton
    Surbiton is a suburban area in southwest London, England, known for its commuter links to central London and its leafy residential character.
  • 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_69b3454965f881908c41190bb22f0e4b completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b351a840248190b88c8a7be9158d25 completed March 12, 2026, 11:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cad46d4081908f685d961d100d42 completed March 27, 2026, 6:22 p.m.
Created at: March 12, 2026, 11:15 p.m.