Triple
T14598322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walton-le-Dale |
E342633
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Higher Walton |
E342634
|
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: Higher Walton | Statement: [Walton-le-Dale, hasNeighbour, Higher Walton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Higher Walton Context triple: [Walton-le-Dale, hasNeighbour, Higher Walton]
-
A.
Higher Walton
chosen
Higher Walton is a village in Lancashire, England, situated near the River Darwen and historically associated with the county’s textile and industrial development.
-
B.
Walton
Walton is a surname most prominently associated with Bill Walton, the Hall of Fame American basketball player and sportscaster.
-
C.
Walton
Walton is a masculine given name of English origin, historically used both as a surname and a first name.
-
D.
Walton
Walton is a nearby settlement to Werrington, likely a small village or locality in the same region of England.
-
E.
Walton
Walton is a village within the City of Wakefield district in West Yorkshire, 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb436d92881908fdf9267568feee2 |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd94ca0fec81908fb9c674f48a793b |
completed | May 8, 2026, 7:46 a.m. |
Created at: April 10, 2026, 1:25 a.m.