Triple
T12509012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heckmondwike |
E299025
|
entity |
| Predicate | locatedNear |
P294
|
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: [Heckmondwike, locatedNear, Dewsbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dewsbury Context triple: [Heckmondwike, locatedNear, 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.
Ilkley
Ilkley is a spa town in West Yorkshire, England, known for its moorland scenery, Victorian architecture, and literary associations.
-
C.
Keighley
Keighley is a historic industrial town in northern England known for its textile heritage and proximity to the Yorkshire Dales.
-
D.
Batley
Batley is a market town in West Yorkshire, England, situated between Leeds and Huddersfield in the metropolitan borough of Kirklees.
-
E.
Chadderton
Chadderton is a town in Greater Manchester, England, historically part of Lancashire and now within the Metropolitan Borough of Oldham.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9541c1ca08190a4026c394ebcbeb5 |
completed | April 10, 2026, 7:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8be566c81908fba8e8caabbd93c |
completed | May 3, 2026, 2:53 a.m. |
Created at: April 8, 2026, 9:57 p.m.