Triple

T23373219
Position Surface form Disambiguated ID Type / Status
Subject Bromham E593530 entity
Predicate near P350 FINISHED
Object Calne NE NERFINISHED

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: Calne | Statement: [Bromham, near, Calne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Calne
Context triple: [Bromham, near, Calne]
  • A. Calne chosen
    Calne is a historic market town in Wiltshire, England, known for its former bacon-curing industry and location in the North Wessex Downs area.
  • B. Swindon
    Swindon is a large town in Wiltshire, England, known as a major commercial and commuter hub in the southwest with strong railway and industrial heritage.
  • C. Yate
    Yate is a town in South Gloucestershire, England, known as a residential and commercial centre north of Bristol.
  • D. Melksham
    Melksham is a market town in western Wiltshire, England, situated on the River Avon and known historically for its woollen industry and later manufacturing.
  • E. Cirencester
    Cirencester is a historic market town in south-central England, renowned for its Roman heritage and Cotswold architecture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d268a50819095f2fd479da8ef3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a3b0bc3c8190b1093f7ea29d015c completed April 29, 2026, 6:22 a.m.
Created at: April 17, 2026, 5:33 p.m.