Triple

T5541951
Position Surface form Disambiguated ID Type / Status
Subject Ripon, North Yorkshire E145308 entity
Predicate hasRiver P165 FINISHED
Object River Ure E128035 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 Ure | Statement: [Ripon, North Yorkshire, hasRiver, River Ure]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Ure
Context triple: [Ripon, North Yorkshire, hasRiver, River Ure]
  • A. River Ure chosen
    The River Ure is a significant river in North Yorkshire, England, flowing through Wensleydale and forming part of the River Ouse system.
  • B. Túr River
    The Túr River is a watercourse in Eastern Europe that flows through parts of Romania and Hungary before joining the Tisa River.
  • C. River Brun
    River Brun is a small river in Lancashire, England, that flows through the town of Burnley and contributes to its local landscape and waterways.
  • D. River Hodder
    River Hodder is a river in Lancashire, England, known for flowing through the Forest of Bowland and joining the River Ribble near Great Mitton.
  • E. River Leen
    The River Leen is a small river in Nottinghamshire, England, that flows through the city of Nottingham before joining the River Trent.
  • 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_69c008fa64888190adae56c8f9ea4031 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01fc7e26481908cec8d0483170ea5 completed March 22, 2026, 4:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69c07d6edb7481908e94de7314ca70cc completed March 22, 2026, 11:38 p.m.
Created at: March 22, 2026, 3:35 p.m.