Triple
T4890825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wearside |
E109554
|
entity |
| Predicate | crossedBy |
P416
|
FINISHED |
| Object | Wearmouth Bridge |
E396410
|
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: Wearmouth Bridge | Statement: [Wearside, crossedBy, Wearmouth Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wearmouth Bridge Context triple: [Wearside, crossedBy, Wearmouth Bridge]
-
A.
Wearmouth Bridge
chosen
Wearmouth Bridge is a historic road bridge spanning the River Wear in Sunderland, England, and is one of the city's most recognizable landmarks.
-
B.
Warrington Bridge
Warrington Bridge is a historic road bridge spanning the River Mersey in Warrington, England, serving as a key local transport crossing.
-
C.
Rea Bridge
Rea Bridge is a bridge spanning the Gloucester and Sharpness Canal in Gloucestershire, England, serving as a crossing point for local road and foot traffic.
-
D.
Esher Bridge
Esher Bridge is a historic road bridge in Esher, Surrey, carrying traffic over the River Mole.
-
E.
Redcliffe Bridge
Redcliffe Bridge is a notable bridge in the suburb of Redcliffe, Western Australia, carrying vehicular traffic across the Swan River as a key local transport link.
- 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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e07ca10819083f80f12374544b1 |
completed | March 20, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0276db4e8819090ece339aba3a13b |
completed | March 22, 2026, 5:31 p.m. |
Created at: March 20, 2026, 1:28 p.m.