Triple
T15156190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Failsworth Pole |
E362082
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Failsworth |
E73663
|
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: Failsworth | Statement: [Failsworth Pole, locatedIn, Failsworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Failsworth Context triple: [Failsworth Pole, locatedIn, Failsworth]
-
A.
Failsworth
chosen
Failsworth is a town in Greater Manchester, England, situated between Manchester and Oldham and known historically for its textile industry.
-
B.
Bedworth
Bedworth is a small market town in Warwickshire, England, situated between Coventry and Nuneaton and known historically for coal mining and ribbon weaving.
-
C.
Haltwhistle
Haltwhistle is a small town in Northumberland, England, known as a gateway to Hadrian’s Wall and the surrounding Tyne Valley countryside.
-
D.
Barrasford
Barrasford is a small village in Northumberland, England, situated in the Tyne Valley and known for its rural setting and proximity to Hadrian’s Wall.
-
E.
Usworth
Usworth is a residential locality within Washington in the metropolitan county of Tyne and Wear in North East England.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060c62b08190bcdbd912d011d1ba |
completed | April 15, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fedd27f2f481909dc26889c973932e |
completed | May 9, 2026, 7:07 a.m. |
Created at: April 10, 2026, 3:08 a.m.