Triple

T6303142
Position Surface form Disambiguated ID Type / Status
Subject RH postcode area E141303 entity
Predicate hasPostTown P2711 FINISHED
Object Betchworth E366127 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: Betchworth | Statement: [RH postcode area, hasPostTown, Betchworth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Betchworth
Context triple: [RH postcode area, hasPostTown, Betchworth]
  • A. Betchworth chosen
    Betchworth is a village in Surrey, England, situated near the North Downs and served by a station on the Mole Valley railway line.
  • B. Bentworth
    Bentworth is a small rural village and civil parish in Hampshire, England, known for its historic church, traditional countryside character, and scenic surroundings.
  • C. Buxworth
    Buxworth is a small village in the High Peak district of Derbyshire, England, known historically for its canal basin and industrial heritage.
  • D. Highworth
    Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
  • E. Bramshott
    Bramshott is a historic village in Hampshire, England, known for its picturesque countryside and association with nearby heathland areas.
  • 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_69c5e436e7ec8190a5ea470eb83ddaea completed March 27, 2026, 1:58 a.m.
Created at: March 22, 2026, 4:27 p.m.