Triple

T11931397
Position Surface form Disambiguated ID Type / Status
Subject South West England E283921 entity
Predicate contains P35 FINISHED
Object Swindon E103379 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: Swindon | Statement: [South West England, contains, Swindon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swindon
Context triple: [South West England, contains, Swindon]
  • A. Swindon chosen
    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.
  • B. Calne
    Calne is a historic market town in Wiltshire, England, known for its former bacon-curing industry and location in the North Wessex Downs area.
  • C. Yeovil
    Yeovil is a town in Somerset, England, known historically for its aircraft and defence industries and serving as a commercial and service hub for the surrounding rural area.
  • D. 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.
  • E. Chippenham
    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.
  • 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_69d6ab2ce9c48190b5d39511b524f666 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90305015c81908edb0d9d3d012b2e completed April 10, 2026, 2:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60a5927c4819088f03206561dfd5f completed May 2, 2026, 2:29 p.m.
Created at: April 8, 2026, 9:45 p.m.