Triple

T7361988
Position Surface form Disambiguated ID Type / Status
Subject WR postcode area E169771 entity
Predicate containsPostTown P2711 FINISHED
Object Pershore E185391 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: Pershore | Statement: [WR postcode area, containsPostTown, Pershore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pershore
Context triple: [WR postcode area, containsPostTown, Pershore]
  • A. Pershore chosen
    Pershore is a historic market town on the River Avon in Worcestershire, England, known for its Georgian architecture and annual plum festival.
  • B. Bridgnorth
    Bridgnorth is a historic market town in Shropshire, England, known for its dramatic position on the River Severn and its high and low town layout linked by a funicular railway.
  • C. Sherborne
    Sherborne is a historic market town in southwest England renowned for its medieval abbey, castles, and well-preserved architecture.
  • D. Sherborne
    Sherborne is a small rural village in West Oxfordshire, England, known for its traditional Cotswold stone buildings and picturesque countryside setting.
  • E. Hednesford
    Hednesford is a small town in Staffordshire, England, situated near Cannock Chase and known historically for its coal mining heritage.
  • 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_69c68a59f2288190877ca15c19b1e822 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f4eb5c808190ba08956bcf297ea8 completed March 27, 2026, 9:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802b90cc081908b15e61921d15b92 completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 3:06 p.m.