Triple
T12842962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooton |
E307098
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Willaston |
E463753
|
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: Willaston | Statement: [Hooton, near, Willaston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Willaston Context triple: [Hooton, near, Willaston]
-
A.
Willaston
chosen
Willaston is a village in Cheshire, England, situated near the town of Crewe.
-
B.
Winsford
Winsford is a town in Cheshire, England, known historically for its salt mining industry and its location along the River Weaver.
-
C.
Wordsley
Wordsley is a suburban village in the West Midlands of England, situated near the town of Stourbridge and historically associated with the region’s glassmaking industry.
-
D.
Myddelton
Myddelton is an alternative historical spelling of the English surname Middleton, associated with various notable British families and figures.
-
E.
Barlaston
Barlaston is a village in Staffordshire, England, known for its rural character and proximity to the city of Stoke-on-Trent.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff2ab60819085561a3120189985 |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b9dc1e48190993430956e0fcfdc |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:35 p.m.