Triple

T15843648
Position Surface form Disambiguated ID Type / Status
Subject Acle Bridge E384159 entity
Predicate crosses P416 FINISHED
Object River Bure E77275 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: River Bure | Statement: [Acle Bridge, crosses, River Bure]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Bure
Context triple: [Acle Bridge, crosses, River Bure]
  • A. River Bure chosen
    The River Bure is a river in Norfolk, England, that flows through the Norfolk Broads before reaching the North Sea near Great Yarmouth.
  • B. River Bain
    River Bain is a river in Lincolnshire, England, known for flowing through the town of Horncastle before joining the River Witham.
  • C. River Bain
    The River Bain is a small river in North Yorkshire, England, known for flowing from Semerwater to join the River Ure near Bainbridge.
  • D. River Gadder
    River Gadder is a small river in Norfolk, England, known as a minor tributary within the local drainage and river network.
  • E. River Brosna
    River Brosna is a river in Ireland that flows through counties such as Westmeath and Offaly before joining the River Shannon.
  • 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142ea3da08190a9d2d5917f84907c completed April 16, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb59bc1f881908c5ed93039e94a46 completed May 9, 2026, 10:30 p.m.
Created at: April 10, 2026, 4:50 a.m.