Triple

T18425902
Position Surface form Disambiguated ID Type / Status
Subject ceremonial county of Wiltshire E447339 entity
Predicate hasTown P847 FINISHED
Object Chippenham 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: Chippenham | Statement: [ceremonial county of Wiltshire, hasTown, Chippenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chippenham
Context triple: [ceremonial county of Wiltshire, hasTown, Chippenham]
  • A. Chippenham chosen
    Chippenham is a historic market town in Wiltshire, England, known for its location on the River Avon and its role as a regional commercial and commuter hub.
  • B. Chippenham
    Chippenham is a village and civil parish in the East Cambridgeshire district of Cambridgeshire, England, known for its rural character and historic estate landscapes.
  • C. 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.
  • D. Cippenham
    Cippenham is a suburban area and former village within the town of Slough in Berkshire, England.
  • E. Banbury
    Banbury is a historic market town in Oxfordshire, England, known for its medieval cross, canal-side setting, and association with the traditional Banbury cake.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51b12606081908ea320fd8d5554c6 completed April 19, 2026, 6:12 p.m.
Created at: April 10, 2026, 11:22 a.m.