Triple

T1955876
Position Surface form Disambiguated ID Type / Status
Subject Huddersfield E42265 entity
Predicate hasNeighbouringTown P3883 FINISHED
Object Dewsbury E54100 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: Dewsbury | Statement: [Huddersfield, hasNeighbouringTown, Dewsbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dewsbury
Context triple: [Huddersfield, hasNeighbouringTown, Dewsbury]
  • A. Dewsbury chosen
    Dewsbury is a market town in West Yorkshire, England, situated between Leeds and Huddersfield on major rail and road routes.
  • B. Keighley
    Keighley is a historic industrial town in northern England known for its textile heritage and proximity to the Yorkshire Dales.
  • C. Batley
    Batley is a market town in West Yorkshire, England, situated between Leeds and Huddersfield in the metropolitan borough of Kirklees.
  • D. Chadderton
    Chadderton is a town in Greater Manchester, England, historically part of Lancashire and now within the Metropolitan Borough of Oldham.
  • E. Brighouse
    Brighouse is a market and industrial town in the metropolitan borough of Calderdale in northern England.
  • 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_69a8870eea088190a38781990812a9bc completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb37b4a38819099f98be92be91ade completed March 7, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae031cc7948190a4d9593cd118c149 completed March 8, 2026, 11:15 p.m.
Created at: March 4, 2026, 7:36 p.m.