Triple
T11921181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evesham weir |
E283657
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Evesham bridge |
E302025
|
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: Evesham bridge | Statement: [Evesham weir, locatedNear, Evesham bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Evesham bridge Context triple: [Evesham weir, locatedNear, Evesham bridge]
-
A.
Evesham Bridge
chosen
Evesham Bridge is a historic road bridge spanning the River Avon in the town of Evesham, Worcestershire, England.
-
B.
Hereford Bridge
Hereford Bridge is a historic stone road bridge in Hereford, England, carrying traffic across the River Wye near the city center.
-
C.
Pershore Bridge
Pershore Bridge is a historic stone road bridge in Pershore, Worcestershire, that carries traffic across the River Avon.
-
D.
Tadcaster Bridge
Tadcaster Bridge is a historic stone road bridge in the town of Tadcaster, North Yorkshire, England, notable for its centuries-old architecture and partial collapse during severe flooding in 2015.
-
E.
Cranborne Bridge
Cranborne Bridge is a historic road bridge in Dorset, England, that spans the River Stour near the village of Cranborne.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e1b08481909ed291667035f330 |
completed | April 10, 2026, 12:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f44033c288819099587af3f895eac5 |
completed | May 1, 2026, 5:54 a.m. |
Created at: April 8, 2026, 9:45 p.m.