Triple
T12555398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Stour (Worcestershire) |
E295200
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Wordsley |
E813918
|
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: Wordsley | Statement: [River Stour (Worcestershire), flowsThrough, Wordsley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wordsley Context triple: [River Stour (Worcestershire), flowsThrough, Wordsley]
-
A.
Wordsley
chosen
Wordsley is a suburban village in the West Midlands of England, situated near the town of Stourbridge and historically associated with the region’s glassmaking industry.
-
B.
Thorley
Thorley is a village and civil parish in Hertfordshire, England, situated just southwest of the town of Bishop's Stortford.
-
C.
Willaston
Willaston is a village in Cheshire, England, situated near the town of Crewe.
-
D.
Rowsley
Rowsley is a village in Derbyshire, England, known for its scenic location near the Peak District and its historic railway and riverside setting.
-
E.
Elsecar
Elsecar is a village in South Yorkshire, England, known for its industrial heritage and preserved railway connections.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95490d2708190857f0cb9b8dd6a30 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65587524881908c933490bface976 |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 11:46 p.m.