Triple

T13254478
Position Surface form Disambiguated ID Type / Status
Subject Rea Bridge E315622 entity
Predicate hasName P744 FINISHED
Object Rea Bridge E315622 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: Rea Bridge | Statement: [Rea Bridge, hasName, Rea Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rea Bridge
Context triple: [Rea Bridge, hasName, Rea Bridge]
  • A. Rea Bridge chosen
    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.
  • B. Maidenhead Bridge
    Maidenhead Bridge is a historic stone road bridge over the River Thames in Berkshire, England, renowned for its elegant arches and role as a key crossing near the town of Maidenhead.
  • C. Leatherhead Bridge
    Leatherhead Bridge is a historic road bridge spanning the River Mole in Leatherhead, Surrey, England.
  • D. Hungerford Bridge
    Hungerford Bridge is a central London railway bridge over the River Thames, flanked by the Golden Jubilee pedestrian bridges and linking Charing Cross station to the South Bank.
  • E. Harwood Bridge
    Harwood Bridge is a major steel truss road bridge in New South Wales, Australia, carrying the Pacific Highway across the Clarence River.
  • 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_69d806b1072881909e46bd212259c5f0 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98f7517048190b4eac4e44e81ff66 completed April 11, 2026, 12:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69fec869957481909ea4fded01851b70 completed May 9, 2026, 5:38 a.m.
Created at: April 9, 2026, 9:24 p.m.