Triple

T2587036
Position Surface form Disambiguated ID Type / Status
Subject Maidenhead E58028 entity
Predicate hasLandmark P105 FINISHED
Object Maidenhead Bridge E408972 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: Maidenhead Bridge | Statement: [Maidenhead, hasLandmark, Maidenhead Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maidenhead Bridge
Context triple: [Maidenhead, hasLandmark, Maidenhead Bridge]
  • A. Maidenhead Bridge chosen
    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.
  • B. Leatherhead Bridge
    Leatherhead Bridge is a historic road bridge spanning the River Mole in Leatherhead, Surrey, England.
  • C. Esher Bridge
    Esher Bridge is a historic road bridge in Esher, Surrey, carrying traffic over the River Mole.
  • 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. Maidenhead Railway Bridge
    Maidenhead Railway Bridge is a historic Brunel-designed railway bridge over the River Thames in England, renowned for its remarkably flat brick arches and elegant engineering.
  • 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_69ab4ac019c8819094add11c46706e32 completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd3f8a3888190889c537e6df07305 completed March 7, 2026, 7:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69b56b217af0819084d8aed695b8377b completed March 14, 2026, 2:05 p.m.
Created at: March 6, 2026, 9:49 p.m.