Triple
T8820172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Burnley |
E209883
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Padiham |
E213204
|
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: Padiham | Statement: [Borough of Burnley, hasSettlement, Padiham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Padiham Context triple: [Borough of Burnley, hasSettlement, Padiham]
-
A.
Padiham
chosen
Padiham is a small town in Lancashire, England, situated near Burnley and known for its industrial heritage and proximity to the River Calder.
-
B.
Pilton
Pilton is a historic suburb and former village now forming part of the town of Barnstaple in North Devon, England.
-
C.
Pilton
Pilton is a residential district in the north of Edinburgh, Scotland, known for its large housing estates and proximity to Granton.
-
D.
Ribblehead
Ribblehead is a remote hamlet in North Yorkshire, England, best known for its dramatic moorland setting and the iconic Ribblehead Viaduct on the Settle–Carlisle railway.
-
E.
Penwortham
Penwortham is a town in Lancashire, England, situated on the south bank of the River Ribble opposite Preston.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600fbbac8190ad36d93fff60a33f |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf89357b488190997f368079ef7e1e |
completed | April 3, 2026, 9:32 a.m. |
Created at: March 30, 2026, 6:46 p.m.