Triple

T8125679
Position Surface form Disambiguated ID Type / Status
Subject Hassocks E189722 entity
Predicate hasPostTown P2711 FINISHED
Object Hassocks E189722 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: Hassocks | Statement: [Hassocks, hasPostTown, Hassocks]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hassocks
Context triple: [Hassocks, hasPostTown, Hassocks]
  • A. Hassocks chosen
    Hassocks is a large village and civil parish in the Mid Sussex district of West Sussex, England, situated just north of the South Downs and known for its commuter links to Brighton and London.
  • 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. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • D. Horsham
    Horsham is a regional city in western Victoria, Australia, serving as a key commercial and service hub for the Wimmera region.
  • E. Beckenham
    Beckenham is a suburban town in southeast London known for its residential character, green spaces, and commuter links into central 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_69ca82bb74848190afb1f18640632c10 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb438eb778819085296e6cbfa2e70d completed March 31, 2026, 3:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69cdc66e6f04819082e58e20557add72 completed April 2, 2026, 1:29 a.m.
Created at: March 30, 2026, 5:34 p.m.