Triple

T23334107
Position Surface form Disambiguated ID Type / Status
Subject Ure Head E591526 entity
Predicate sourceOf P409 FINISHED
Object River Ure NE NERFINISHED

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: [Ure Head, sourceOf, River Ure]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Ure
Context triple: [Ure Head, sourceOf, 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. River Urie
    River Urie is a small river in Aberdeenshire, Scotland, known for flowing through the town of Inverurie before joining the River Don.
  • C. River Urr
    River Urr is a river in southwest Scotland that flows through Dumfries and Galloway before entering the Solway Firth.
  • D. River Kesh
    River Kesh is a lesser-known river in Ireland that serves as a tributary of the River Erne, contributing to its catchment in the northwest of the country.
  • E. River Shee
    River Shee is a Scottish river flowing through the scenic Highland valley of Glen Shee in eastern Perth and Kinross.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197efd98c819083635a2b8440f3eb completed April 29, 2026, 5:32 a.m.
Created at: April 17, 2026, 5:16 p.m.