Triple

T6490003
Position Surface form Disambiguated ID Type / Status
Subject Esher Bridge E148010 entity
Predicate hasName P744 FINISHED
Object Esher Bridge E148010 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: Esher Bridge | Statement: [Esher Bridge, hasName, Esher Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Esher Bridge
Context triple: [Esher Bridge, hasName, Esher Bridge]
  • A. Esher Bridge chosen
    Esher Bridge is a historic road bridge in Esher, Surrey, carrying traffic over the River Mole.
  • B. Ryde Bridge
    Ryde Bridge is a road bridge in Sydney, Australia, that carries traffic across the Parramatta River between the suburbs of Ryde and Rhodes.
  • C. Maidenhead Bridge
    Maidenhead Bridge is a historic stone road bridge over the River Thames in Berkshire, England, renowned for its elegant arches and role as a key crossing near the town of Maidenhead.
  • D. Warrington Bridge
    Warrington Bridge is a historic road bridge spanning the River Mersey in Warrington, England, serving as a key local transport crossing.
  • E. Fitzherbert Bridge
    Fitzherbert Bridge is a major road bridge in Palmerston North, New Zealand, serving as a key crossing and transport link over the Manawatū River.
  • 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_69c009088f3081909cd467b05919de30 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a9926fc81909db0f390e385e97d completed March 22, 2026, 10:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8569b932481909d41130303e21518 completed March 28, 2026, 10:30 p.m.
Created at: March 22, 2026, 4:52 p.m.