Triple
T9831389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Much Hoole |
E238991
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Longton, Lancashire |
E697353
|
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: Longton, Lancashire | Statement: [Much Hoole, locatedNear, Longton, Lancashire]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longton, Lancashire Context triple: [Much Hoole, locatedNear, Longton, Lancashire]
-
A.
Longton
Longton is a town in Stoke-on-Trent, Staffordshire, England, historically known as one of the six pottery towns of the region.
-
B.
Longton
chosen
Longton is a village in Lancashire, England, situated within the South Ribble district and known for its semi-rural character and commuter links to nearby Preston.
-
C.
Northenden
Northenden is a suburban area of Manchester, England, situated on the River Mersey in the south of the city.
-
D.
Huyton
Huyton is a suburban town in North West England that forms part of the Metropolitan Borough of Knowsley within the Merseyside conurbation.
-
E.
Egremont, Lancashire, England
Egremont, Lancashire, England is a small village in the North West of England, historically part of the county of Lancashire.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3297bd88190bf8c53a4ba00e0ae |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e41e1b8081908ef5bb31c27c5264 |
completed | April 5, 2026, 4:25 a.m. |
Created at: March 30, 2026, 8:32 p.m.