Triple
T15376878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calderdale river network |
E367690
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Brighouse |
E150944
|
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: Brighouse | Statement: [Calderdale river network, flowsThrough, Brighouse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brighouse Context triple: [Calderdale river network, flowsThrough, Brighouse]
-
A.
Brighouse
chosen
Brighouse is a market and industrial town in the metropolitan borough of Calderdale in northern England.
-
B.
Milnrow
Milnrow is a town in Greater Manchester, England, historically part of Lancashire and known for its textile heritage and proximity to the Pennine hills.
-
C.
Hepple
Hepple is a small rural village in Northumberland, England, situated in the scenic Coquet Valley.
-
D.
Salterforth
Salterforth is a small rural village in Lancashire, England, situated near the Leeds and Liverpool Canal and known for its scenic countryside setting.
-
E.
Hunslet
Hunslet is an inner-city district of Leeds in West Yorkshire, England, historically known for its industrial heritage and engineering works.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5ece1081908d7c1289258b9c1f |
completed | April 16, 2026, 1:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1347c8448190aa1088d66bca2722 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:18 a.m.