Triple

T6665969
Position Surface form Disambiguated ID Type / Status
Subject River Ant E151603 entity
Predicate flowsThrough P225 FINISHED
Object Ludham Bridge E689170 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: Ludham Bridge | Statement: [River Ant, flowsThrough, Ludham Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ludham Bridge
Context triple: [River Ant, flowsThrough, Ludham Bridge]
  • A. Stopham Bridge
    Stopham Bridge is a historic medieval stone arch bridge in West Sussex, England, noted for its picturesque setting and architectural significance.
  • B. Cobham Bridge
    Cobham Bridge is a road bridge in Surrey, England, that carries traffic across the River Mole near the village of Cobham.
  • C. Wroxham Bridge
    Wroxham Bridge is a historic low-arched road bridge in the Norfolk Broads, England, known as a key boating landmark and one of the most challenging navigational points on the River Bure.
  • D. Totnes Bridge
    Totnes Bridge is a historic stone road bridge in the town of Totnes, Devon, England, notable for carrying traffic across the River Dart.
  • E. Wayford Bridge chosen
    Wayford Bridge is a small riverside settlement and crossing point in the Norfolk Broads of England, known for its boating access and scenic waterways.
  • 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_69c687f71fc081909dbd45d6377f6045 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b09d97648190a254cabc0ffcb0dc completed March 27, 2026, 4:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8fa179c008190a6bba55cb62b7fe8 completed March 29, 2026, 10:08 a.m.
Created at: March 27, 2026, 2:02 p.m.