Triple

T3179859
Position Surface form Disambiguated ID Type / Status
Subject Kew E66556 entity
Predicate hasBridge P386 FINISHED
Object Kew Bridge E354621 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: Kew Bridge | Statement: [Kew, hasBridge, Kew Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kew Bridge
Context triple: [Kew, hasBridge, Kew Bridge]
  • A. Kew Bridge chosen
    Kew Bridge is a historic road bridge over the River Thames in west London, linking the districts of Kew and Brentford.
  • B. Chertsey Bridge
    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.
  • C. Twickenham Bridge
    Twickenham Bridge is an arched road bridge over the River Thames in southwest London, linking Richmond and St Margarets and carrying the A316.
  • 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_69ad8586a34c8190944c63ec11a8de1a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada69f2d108190847922795e7b6687 completed March 8, 2026, 4:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69b555ff48c48190865f0d588ec5d296 completed March 14, 2026, 12:35 p.m.
Created at: March 8, 2026, 3:06 p.m.