Triple
T5518178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poynton |
E144736
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Adlington |
E185613
|
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: Adlington | Statement: [Poynton, near, Adlington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adlington Context triple: [Poynton, near, Adlington]
-
A.
Adlington
chosen
Adlington is a small town in Lancashire, England, situated near Horwich and known historically for its role in the region’s textile and coal industries.
-
B.
Walkden
Walkden is a suburban town in the City of Salford, Greater Manchester, England, with its own railway station on the Atherton line.
-
C.
Colne
Colne is a historic market town in Lancashire, England, known for its textile heritage and location near the Pennine hills.
-
D.
Congleton
Congleton is a historic market town in the county of Cheshire in North West England, known for its industrial heritage and riverside setting.
-
E.
Northenden
Northenden is a suburban area of Manchester, England, situated on the River Mersey in the south of the city.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f6cefe48190bfda90d6afab8468 |
completed | March 22, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027e1ed4c81908f670286556ced81 |
completed | March 22, 2026, 5:33 p.m. |
Created at: March 22, 2026, 3:33 p.m.