Triple

T6303151
Position Surface form Disambiguated ID Type / Status
Subject RH postcode area E141303 entity
Predicate hasPostTown P2711 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: [RH postcode area, hasPostTown, Coulsdon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Coulsdon
Context triple: [RH postcode area, hasPostTown, 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645e150881908b49a07914dcbfd8 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c9061044ac8190b204f5002955df72 completed March 29, 2026, 10:59 a.m.
Created at: March 22, 2026, 4:27 p.m.