Triple

T1282362
Position Surface form Disambiguated ID Type / Status
Subject Chertsey E27353 entity
Predicate hasBridge P386 FINISHED
Object Chertsey Bridge E203550 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: Chertsey Bridge | Statement: [Chertsey, hasBridge, Chertsey Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chertsey Bridge
Context triple: [Chertsey, hasBridge, Chertsey Bridge]
  • A. Chertsey Bridge chosen
    Chertsey Bridge is an 18th-century stone arch bridge over the River Thames in England, known for its historic architecture and role in connecting Chertsey with surrounding areas.
  • B. Esher Bridge
    Esher Bridge is a historic road bridge in Esher, Surrey, carrying traffic over the River Mole.
  • C. Cobham Bridge
    Cobham Bridge is a road bridge in Surrey, England, that carries traffic across the River Mole near the village of Cobham.
  • D. Burton Bridge
    Burton Bridge is a historic road bridge in Burton upon Trent, Staffordshire, England, known for carrying traffic across the River Trent and shaping the town’s development.
  • E. 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.
  • 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_69a496d3710c8190955dee8bc0dacb50 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c0b47be08190828a1c0a11d94ce8 completed March 1, 2026, 10:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69adc97fe2808190b421329ed239af6f completed March 8, 2026, 7:09 p.m.
Created at: March 1, 2026, 7:50 p.m.