Triple
T14039826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sale, Greater Manchester |
E337814
|
entity |
| Predicate | hasSuburb |
P747
|
FINISHED |
| Object | Ashton upon Mersey |
E1075142
|
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: Ashton upon Mersey | Statement: [Sale, Greater Manchester, hasSuburb, Ashton upon Mersey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashton upon Mersey Context triple: [Sale, Greater Manchester, hasSuburb, Ashton upon Mersey]
-
A.
Ashton upon Mersey
chosen
Ashton upon Mersey is a suburban area within the town of Sale in Greater Manchester, England, known for its residential character and local schools.
-
B.
Leasowe
Leasowe is a coastal residential area on the Wirral Peninsula in Merseyside, England, known for its beach, sand dunes, and historic Leasowe Lighthouse.
-
C.
Willaston
Willaston is a village in Cheshire, England, situated near the town of Crewe.
-
D.
Heaton Mersey
Heaton Mersey is a suburban area of Stockport in Greater Manchester, England, known for its residential character and proximity to the River Mersey.
-
E.
Winsford
Winsford is a town in Cheshire, England, known historically for its salt mining industry and its location along the River Weaver.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de30ee374081908b6b5e8f81dd90f2 |
completed | April 14, 2026, 12:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb65a21088190a14808d09b2b9f42 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:20 p.m.