Triple

T8780918
Position Surface form Disambiguated ID Type / Status
Subject Coulsdon E208722 entity
Predicate near P350 FINISHED
Object Old 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: Old Coulsdon | Statement: [Coulsdon, near, Old Coulsdon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Coulsdon
Context triple: [Coulsdon, near, Old 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. Earlswood
    Earlswood is a residential suburb and locality in Surrey, England, situated just south of the town of Redhill.
  • C. East Horsley
    East Horsley is a village and civil parish in Surrey, England, known for its affluent residential character and location within the Surrey Hills area.
  • D. Woldingham
    Woldingham is a rural village and civil parish in Surrey, England, known for its affluent residential character and location on the North Downs.
  • E. Chieveley
    Chieveley is a rural village and civil parish in Berkshire, England, known for its historic church, countryside setting, and proximity to Newbury and major transport routes.
  • 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_69ca835fbee88190bf625939bac48d7f completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f55b7b08190ab3e18cd634a144b completed March 31, 2026, 11:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf51df4a608190883a093dbd169976 completed April 3, 2026, 5:36 a.m.
Created at: March 30, 2026, 6:42 p.m.