Triple
T3242594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkby |
E67995
|
entity |
| Predicate | hasNeighbouringSettlement |
P4647
|
FINISHED |
| Object | Maghull |
E89627
|
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: Maghull | Statement: [Kirkby, hasNeighbouringSettlement, Maghull]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maghull Context triple: [Kirkby, hasNeighbouringSettlement, Maghull]
-
A.
Maghull
chosen
Maghull is a suburban town in Merseyside, England, situated to the north of Liverpool and functioning largely as a residential commuter area.
-
B.
Wallasey
Wallasey is a coastal town on the Wirral Peninsula in northwest England, situated at the mouth of the River Mersey opposite Liverpool.
-
C.
Saltney
Saltney is a town near the England–Wales border, close to Chester, known historically for its industrial activity and proximity to the River Dee.
-
D.
Barrow-in-Furness
Barrow-in-Furness is a coastal industrial town in Cumbria, England, historically known for its shipbuilding and submarine construction.
-
E.
Poulton-le-Fylde
Poulton-le-Fylde is a historic market town in Lancashire, England, known for its traditional town centre and proximity to the seaside resort of Blackpool.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf17463481909447f6ab46016407 |
completed | March 8, 2026, 5:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b28eadeff481909bd48cdf51044f86 |
completed | March 12, 2026, 10 a.m. |
Created at: March 8, 2026, 3:08 p.m.