Triple

T6737716
Position Surface form Disambiguated ID Type / Status
Subject Acle E153998 entity
Predicate hasRiver P165 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, hasRiver, River Bure]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Bure
Context triple: [Acle, hasRiver, 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 Brosna
    River Brosna is a river in Ireland that flows through counties such as Westmeath and Offaly before joining the River Shannon.
  • D. Đáy River
    Đáy River is a significant river in northern Vietnam that flows through several provinces and districts, serving as an important waterway and agricultural resource.
  • E. River Roden
    River Roden is a small river in Shropshire, England, that flows through rural countryside before joining the River Tern.
  • 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_69c70b0b97248190bf6bac160fe3d45b completed March 27, 2026, 10:56 p.m.
Created at: March 27, 2026, 2:10 p.m.