Triple

T6303139
Position Surface form Disambiguated ID Type / Status
Subject RH postcode area E141303 entity
Predicate hasPostTown P2711 FINISHED
Object Burgess Hill E255320 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: Burgess Hill | Statement: [RH postcode area, hasPostTown, Burgess Hill]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burgess Hill
Context triple: [RH postcode area, hasPostTown, Burgess Hill]
  • A. Burgess Hill chosen
    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.
  • B. Purley
    Purley is a suburban town in South London known for its residential character and location within the London Borough of Croydon.
  • C. Redhill
    Redhill is a commuter town in southeast England known for its transport links and proximity to London within the county of Surrey.
  • D. Surbiton
    Surbiton is a suburban area in southwest London, England, known for its commuter links to central London and its leafy residential character.
  • E. 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.
  • 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_69c902a459f481908dbba16de611b85a completed March 29, 2026, 10:44 a.m.
Created at: March 22, 2026, 4:27 p.m.