Triple

T21388979
Position Surface form Disambiguated ID Type / Status
Subject Hampton Court Way E527586 entity
Predicate crossesVia P416 FINISHED
Object Hampton Court Bridge NE NERFINISHED

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: Hampton Court Bridge | Statement: [Hampton Court Way, crossesVia, Hampton Court Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hampton Court Bridge
Context triple: [Hampton Court Way, crossesVia, Hampton Court Bridge]
  • A. Hampton Court Bridge chosen
    Hampton Court Bridge is a historic road bridge in southwest London that carries traffic across the River Thames near Hampton Court Palace, linking Hampton in London with East Molesey in Surrey.
  • B. Arundel Bridge
    Arundel Bridge is a historic road bridge in the town of Arundel, West Sussex, England, carrying traffic across the River Arun.
  • C. 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.
  • D. Deptford Bridge
    Deptford Bridge is a Docklands Light Railway station in southeast London serving the Deptford area near Greenwich.
  • 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 (2 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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee62cbfef08190a33ac1f198c82cd0 completed April 26, 2026, 7:09 p.m.
Created at: April 16, 2026, 5:12 p.m.