Triple
T11495762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD postcode area |
E272529
|
entity |
| Predicate | coversTown |
P847
|
FINISHED |
| Object | Farsley |
E826678
|
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: Farsley | Statement: [BD postcode area, coversTown, Farsley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Farsley Context triple: [BD postcode area, coversTown, Farsley]
-
A.
Farsley
chosen
Farsley is a suburban village in West Yorkshire, England, situated between Leeds and Bradford.
-
B.
Fritchley
Fritchley is a small village in Derbyshire, England, known for its rural character and proximity to the larger village of Crich.
-
C.
Frosterley
Frosterley is a small village in County Durham, England, situated in the rural Weardale valley and known historically for its quarrying and distinctive “Frosterley marble.”
-
D.
Farnworth
Farnworth is a town in Greater Manchester, England, historically part of Lancashire and now largely residential with local industry and transport links to nearby urban centers.
-
E.
Helsby
Helsby is a village and civil parish in Cheshire, England, known for its railway station on the Manchester–Chester line and its prominent sandstone hill, Helsby Hill.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6048a05c88190968f7827c5dd5342 |
completed | April 20, 2026, 10:48 a.m. |
Created at: April 8, 2026, 9:36 p.m.