Triple

T6843971
Position Surface form Disambiguated ID Type / Status
Subject O’Connell Bridge E157844 entity
Predicate rebuiltFrom P11047 FINISHED
Object Carlisle Bridge E690340 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: Carlisle Bridge | Statement: [O’Connell Bridge, rebuiltFrom, Carlisle Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Carlisle Bridge
Context triple: [O’Connell Bridge, rebuiltFrom, Carlisle Bridge]
  • A. Carlisle Bridge chosen
    Carlisle Bridge was the 18th–19th century bridge over Dublin’s River Liffey that originally carried traffic where O’Connell Bridge now stands.
  • B. Cotter Bridge
    Cotter Bridge is a historic steel arch bridge in Cotter, Arkansas, that spans the White River and is noted for its distinctive rainbow-arch design.
  • C. Ludford Bridge
    Ludford Bridge is a historic stone road bridge in Ludlow, Shropshire, England, known for carrying traffic across the River Teme near the town’s medieval center.
  • D. Hereford Bridge
    Hereford Bridge is a historic stone road bridge in Hereford, England, carrying traffic across the River Wye near the city center.
  • 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_69c6882ed4c081909dc465a7cf8838be completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d6b7179481909e3482fef47b2719 completed March 27, 2026, 7:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c934b54a7c81909cdccd01af24c73d completed March 29, 2026, 2:18 p.m.
Created at: March 27, 2026, 2:19 p.m.