Triple

T5852749
Position Surface form Disambiguated ID Type / Status
Subject A316 road E130074 entity
Predicate bridgeUsed P30350 FINISHED
Object Twickenham Bridge E352474 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: Twickenham Bridge | Statement: [A316 road, bridgeUsed, Twickenham Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Twickenham Bridge
Context triple: [A316 road, bridgeUsed, Twickenham Bridge]
  • A. Twickenham Bridge chosen
    Twickenham Bridge is an arched road bridge over the River Thames in southwest London, linking Richmond and St Margarets and carrying the A316.
  • B. Hammersmith Bridge
    Hammersmith Bridge is a historic 19th-century suspension bridge in west London that carries traffic across the River Thames between Hammersmith and Barnes.
  • C. Wandsworth Bridge
    Wandsworth Bridge is a road bridge over the River Thames in southwest London, connecting the boroughs of Wandsworth and Hammersmith and Fulham.
  • D. Esher Bridge
    Esher Bridge is a historic road bridge in Esher, Surrey, carrying traffic over the River Mole.
  • E. Battersea Bridge
    Battersea Bridge is a road and foot traffic bridge over the River Thames in London, connecting the districts of Battersea and Chelsea.
  • 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_69c0084de39081909eb34e6bed74215a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0355038008190bf38980349b533e2 completed March 22, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e369ce248190af33d7c09ee10af6 completed March 23, 2026, 6:53 a.m.
Created at: March 22, 2026, 3:55 p.m.