Triple

T3556123
Position Surface form Disambiguated ID Type / Status
Subject Ilchester E75222 entity
Predicate near P350 FINISHED
Object Yeovil E74538 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: Yeovil | Statement: [Ilchester, near, Yeovil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeovil
Context triple: [Ilchester, near, Yeovil]
  • A. Yeovil chosen
    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.
  • B. Torquay
    Torquay is a seaside resort town on the English Riviera in Devon, England, known for its mild climate, beaches, and Victorian-era tourism.
  • C. 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.
  • D. Yeovilton
    Yeovilton is a village in Somerset, England, best known for its Royal Naval Air Station and strong association with British naval aviation.
  • E. Verwood
    Verwood is a small town in eastern Dorset, England, known for its rural character and proximity to the New Forest and Cranborne Chase.
  • 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_69ad85d45090819086f34fb85d850a1e completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc057cc788190a6c4f3781f43abce completed March 8, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b432fdda488190a31f74e80685c121 completed March 13, 2026, 3:53 p.m.
Created at: March 8, 2026, 3:20 p.m.