Triple
T7597620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lancashire Line |
E179896
|
entity |
| Predicate | servesTown |
P847
|
FINISHED |
| Object | Colne |
E179903
|
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: Colne | Statement: [East Lancashire Line, servesTown, Colne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Colne Context triple: [East Lancashire Line, servesTown, Colne]
-
A.
Colne
chosen
Colne is a historic market town in Lancashire, England, known for its textile heritage and location near the Pennine hills.
-
B.
Barnoldswick
Barnoldswick is a small market town in Lancashire, England, known for its industrial heritage and scenic location near the Yorkshire Dales.
-
C.
Bacup
Bacup is a small former mill town in Lancashire, England, known for its well-preserved Victorian architecture and industrial heritage in the South Pennines.
-
D.
Adlington
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.
-
E.
Consett
Consett is a town in north-west County Durham, England, historically known for its steelworks and industrial heritage.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d4d3408190b9650347c7850c47 |
completed | March 27, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c870858c648190acbbad9b5bb12ba4 |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:53 p.m.