Triple

T22269259
Position Surface form Disambiguated ID Type / Status
Subject Ringsend Road, Dublin E550431 entity
Predicate hasBridge P386 FINISHED
Object Ringsend Bridge NE NERFINISHED

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: Ringsend Bridge | Statement: [Ringsend Road, Dublin, hasBridge, Ringsend Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ringsend Bridge
Context triple: [Ringsend Road, Dublin, hasBridge, Ringsend Bridge]
  • A. Ringsend Bridge chosen
    Ringsend Bridge is a historic road bridge in Dublin, Ireland, that spans the River Dodder and connects the Ringsend area with the city’s southside.
  • B. Chapelizod Bridge
    Chapelizod Bridge is a historic stone road bridge over the River Liffey in the village of Chapelizod, Dublin, Ireland.
  • C. Fermoy Bridge
    Fermoy Bridge is a historic stone road bridge spanning the River Blackwater in the town of Fermoy, County Cork, Ireland.
  • D. Sarsfield Bridge
    Sarsfield Bridge is a historic road and pedestrian bridge spanning the River Shannon in Limerick, Ireland.
  • E. Inistioge Bridge
    Inistioge Bridge is a historic multi-arched stone bridge in County Kilkenny, Ireland, noted for its picturesque setting and architectural charm.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e43d8208190aff4f9cf7f2c2a8a completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f141bde9f88190b533bcb88787b492 completed April 28, 2026, 11:24 p.m.
Created at: April 16, 2026, 8:40 p.m.