Triple

T6540066
Position Surface form Disambiguated ID Type / Status
Subject Wetherby E168262 entity
Predicate hasPostTown P2711 FINISHED
Object WETHERBY E168262 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: WETHERBY | Statement: [Wetherby, hasPostTown, WETHERBY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: WETHERBY
Context triple: [Wetherby, hasPostTown, WETHERBY]
  • A. Wetherby chosen
    Wetherby is a market town in West Yorkshire, England, situated on the River Wharfe and known historically as a key coaching stop between London and Edinburgh.
  • B. Wyre
    Wyre is a district and local government area in Lancashire, England, named after the River Wyre and known for its mix of coastal towns and rural countryside.
  • C. Westerdale
    Westerdale is a small rural village and civil parish in the North York Moors of North Yorkshire, England, known for its moorland scenery and agricultural landscape.
  • D. Warton
    Warton is a small English village in Lancashire known for its historic buildings and scenic setting near the Arnside and Silverdale coastline.
  • E. Langworthy
    Langworthy is a residential district in Salford, Greater Manchester, known for its urban regeneration and proximity to Manchester city centre.
  • 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_69c68a51564081909e93aee0dbd9cca3 completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6add5d3848190a0d70dc4013ab756 completed March 27, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d53b861c81908adc984a3067d4ef completed March 27, 2026, 7:06 p.m.
Created at: March 27, 2026, 1:50 p.m.