Triple
T11514188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Colne (Lancashire) |
E272988
|
entity |
| Predicate | namedAfter |
P63
|
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: [River Colne (Lancashire), namedAfter, Colne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Colne Context triple: [River Colne (Lancashire), namedAfter, 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.
Cornholme
Cornholme is a village in West Yorkshire, England, situated in the Upper Calder Valley near Todmorden.
-
C.
Rothwell
Rothwell is a town in Northamptonshire, England, situated near Kettering and known for its historic market heritage.
-
D.
Barnoldswick
Barnoldswick is a small market town in Lancashire, England, known for its industrial heritage and scenic location near the Yorkshire Dales.
-
E.
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.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db8bf9c8190820c289e6b0c3873 |
completed | April 10, 2026, 3:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6852a23688190a3fe8e5508435661 |
completed | April 20, 2026, 7:57 p.m. |
Created at: April 8, 2026, 9:36 p.m.