Triple

T6915266
Position Surface form Disambiguated ID Type / Status
Subject Cobham Bridge E160033 entity
Predicate hasName P744 FINISHED
Object Cobham Bridge E160033 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: Cobham Bridge | Statement: [Cobham Bridge, hasName, Cobham Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cobham Bridge
Context triple: [Cobham Bridge, hasName, Cobham Bridge]
  • A. Cobham Bridge chosen
    Cobham Bridge is a road bridge in Surrey, England, that carries traffic across the River Mole near the village of Cobham.
  • B. Sandfield Bridge
    Sandfield Bridge is a road bridge spanning the Gloucester and Sharpness Canal in Gloucestershire, England.
  • C. Stopham Bridge
    Stopham Bridge is a historic medieval stone arch bridge in West Sussex, England, noted for its picturesque setting and architectural significance.
  • D. Lazonby Bridge
    Lazonby Bridge is a historic stone road bridge spanning the River Eden near the village of Lazonby in Cumbria, England.
  • E. Catford Bridge
    Catford Bridge is a railway station in southeast London that provides suburban rail services connecting the area to central London and other parts of the city.
  • 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_69c6883ab1008190a07129ff06f625d9 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6d9dec058819094d1913a1e5218c0 completed March 27, 2026, 7:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c95675f24c81909f9c14e29a79c157 completed March 29, 2026, 4:42 p.m.
Created at: March 27, 2026, 2:26 p.m.