Triple
T5811391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bewdley |
E128874
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | BEWDLEY |
E128874
|
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: BEWDLEY | Statement: [Bewdley, postTown, BEWDLEY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BEWDLEY Context triple: [Bewdley, postTown, BEWDLEY]
-
A.
Bewdley
chosen
Bewdley is a historic riverside town in Worcestershire, England, known for its Georgian architecture and picturesque setting on the River Severn.
-
B.
Banwell
Banwell is a village and civil parish in North Somerset, England, known for its historic caves and medieval architecture.
-
C.
Beverley
Beverley is a historic market town and civil parish in the East Riding of Yorkshire, England, known for its impressive Gothic minster and medieval architecture.
-
D.
Beswick
Beswick is an inner-city district of Manchester, England, known for its industrial heritage and ongoing urban regeneration.
-
E.
Sawley
Sawley is a village in Derbyshire, England, situated near the town of Long Eaton on the River Trent.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b54c2848190bb85212689d0b511 |
completed | March 22, 2026, 5:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c09844f0b881908d4165e550f75d47 |
completed | March 23, 2026, 1:32 a.m. |
Created at: March 22, 2026, 3:52 p.m.