Triple

T3584513
Position Surface form Disambiguated ID Type / Status
Subject Richmond, Surrey, England E75879 entity
Predicate hasLandmark P105 FINISHED
Object Richmond Bridge E48167 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: Richmond Bridge | Statement: [Richmond, Surrey, England, hasLandmark, Richmond Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richmond Bridge
Context triple: [Richmond, Surrey, England, hasLandmark, Richmond Bridge]
  • A. Richmond Bridge chosen
    Richmond Bridge is an 18th-century stone arch bridge in southwest London, renowned as the oldest surviving bridge across the River Thames in the city.
  • B. Kingston Bridge
    Kingston Bridge is a major motorway bridge in Glasgow, Scotland, carrying the M8 over the River Clyde and serving as one of the city’s busiest road crossings.
  • C. Kingston Bridge
    Kingston Bridge is a historic road bridge over the River Thames in southwest London, linking Kingston upon Thames with Hampton Wick.
  • D. Runnymede Bridge
    Runnymede Bridge is a road bridge over the River Thames in Surrey, England, carrying the M25 motorway near the historic meadow of Runnymede.
  • E. Queen’s Bridge
    Queen’s Bridge is a historic bridge in Bound Brook, New Jersey, known for carrying traffic across the Raritan River and serving as a key local crossing point.
  • 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_69ad85d6dc3c8190b491b79b83e25461 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc10f9b508190bde4a4e4711dd452 completed March 8, 2026, 6:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69befe3ba3848190bcd62dd21229ca67 completed March 21, 2026, 8:23 p.m.
Created at: March 8, 2026, 3:21 p.m.