Triple
T7973617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rice Lake |
E185386
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
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: [Rice Lake, hasNearbySettlement, Bewdley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bewdley Context triple: [Rice Lake, hasNearbySettlement, 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.
Bardwell
Bardwell is a small rural village and civil parish in the county of Suffolk in eastern England.
-
C.
Bleasdale
Bleasdale is a small rural village and civil parish in Lancashire, England, situated on the edge of the Forest of Bowland Area of Outstanding Natural Beauty.
-
D.
Beachamwell
Beachamwell is a small rural village in Norfolk, England, known for its traditional countryside setting and historic parish church.
-
E.
Belchford
Belchford is a small rural village in eastern England, situated within the scenic, rolling countryside of the Lincolnshire Wolds.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf319648190a900b133d58bd02b |
completed | March 31, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc56710dd0819084da3898cb0933b0 |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:13 p.m.