Triple
T1425850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runcorn Railway Bridge |
E30329
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Runcorn |
E15158
|
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: Runcorn | Statement: [Runcorn Railway Bridge, locatedIn, Runcorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runcorn Context triple: [Runcorn Railway Bridge, locatedIn, Runcorn]
-
A.
Runcorn
chosen
Runcorn is an industrial town in Cheshire, England, situated on the southern bank of the River Mersey and known for its chemical industry and transport links.
-
B.
Ellesmere Port
Ellesmere Port is an industrial town and port in Cheshire, England, known for its docks on the Manchester Ship Canal and proximity to Liverpool.
-
C.
Widnes
Widnes is an industrial town in Cheshire, England, historically known for its chemical industry and location on the River Mersey.
-
D.
Maghull
Maghull is a suburban town in Merseyside, England, situated to the north of Liverpool and functioning largely as a residential commuter area.
-
E.
Wallasey
Wallasey is a coastal town on the Wirral Peninsula in northwest England, situated at the mouth of the River Mersey opposite Liverpool.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c4bd59148190b96f9f585e07aa0d |
completed | March 1, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad01646fd481909fcd92a1cc027fa2 |
completed | March 8, 2026, 4:56 a.m. |
Created at: March 1, 2026, 8 p.m.