Triple

T6737743
Position Surface form Disambiguated ID Type / Status
Subject Acle E153998 entity
Predicate hasNearbyWaterway P8567 FINISHED
Object Acle Bridge E384159 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: Acle Bridge | Statement: [Acle, hasNearbyWaterway, Acle Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Acle Bridge
Context triple: [Acle, hasNearbyWaterway, Acle Bridge]
  • A. Acle Bridge chosen
    Acle Bridge is a historic road bridge in Norfolk, England, that carries traffic across the River Bure within the Norfolk Broads.
  • B. Wayford Bridge
    Wayford Bridge is a small riverside settlement and crossing point in the Norfolk Broads of England, known for its boating access and scenic waterways.
  • C. Bewdley Bridge
    Bewdley Bridge is a historic stone arch bridge over the River Severn in Bewdley, Worcestershire, England, designed by the renowned engineer Thomas Telford.
  • D. Clopton Bridge
    Clopton Bridge is a historic stone road bridge over the River Avon in Stratford-upon-Avon, England, dating back to the late 15th century.
  • E. Wye Bridge
    Wye Bridge is a road bridge spanning the River Wye near its confluence with the River Severn, forming part of the approach to the Severn Bridge between England and Wales.
  • 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_69c6880d84d8819095d19de2295f26ac completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d1850a288190aa7e647fefbb0ede completed March 27, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69c91f3e6cec8190ad66e8f4feb6b911 completed March 29, 2026, 12:46 p.m.
Created at: March 27, 2026, 2:10 p.m.