Triple
T4368960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Paul’s Church, Blackley |
E98846
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Blackley |
E17502
|
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: Blackley | Statement: [St Paul’s Church, Blackley, locatedIn, Blackley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blackley Context triple: [St Paul’s Church, Blackley, locatedIn, Blackley]
-
A.
Blackley
chosen
Blackley is a suburban area of Manchester, England, known for its residential neighborhoods and proximity to the River Irk and local green spaces.
-
B.
Kearsley
Kearsley is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
-
C.
Kirkley
Kirkley is a coastal suburb and former village now forming part of the town of Lowestoft in Suffolk, England.
-
D.
Hockley
Hockley is a village in Essex, England, known for its residential character and rail links to London and Southend.
-
E.
Ubley
Ubley is a small rural village in Somerset, England, situated near the northern edge of the Mendip Hills.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352052b388190b02cca9a3b480be4 |
completed | March 12, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5f5d4612c8190ac5163d50299f8ab |
completed | March 14, 2026, 11:57 p.m. |
Created at: March 12, 2026, 11:17 p.m.