Triple
T831872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Mole |
E17982
|
entity |
| Predicate | passesUnder |
P19079
|
FINISHED |
| Object | Cobham Bridge |
E148010
|
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: Cobham Bridge | Statement: [River Mole, passesUnder, Cobham Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cobham Bridge Context triple: [River Mole, passesUnder, Cobham Bridge]
-
A.
Burton Bridge
Burton Bridge is a historic road bridge in Burton upon Trent, Staffordshire, England, known for carrying traffic across the River Trent and shaping the town’s development.
-
B.
Leatherhead Bridge
Leatherhead Bridge is a historic road bridge spanning the River Mole in Leatherhead, Surrey, England.
-
C.
Runnymede Bridge
Runnymede Bridge is a road bridge over the River Thames in Surrey, England, carrying the M25 motorway near the historic meadow of Runnymede.
-
D.
Esher Bridge
chosen
Esher Bridge is a historic road bridge in Esher, Surrey, carrying traffic over the River Mole.
-
E.
Warrington Bridge
Warrington Bridge is a historic road bridge spanning the River Mersey in Warrington, England, serving as a key local transport crossing.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb4be948190ae757df85bdc40e4 |
completed | March 1, 2026, 9:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbf0330b4819089042160ff199336 |
completed | March 8, 2026, 12:12 a.m. |
Created at: March 1, 2026, 7:38 p.m.