Triple

T16743943
Position Surface form Disambiguated ID Type / Status
Subject Newby Hall E406900 entity
Predicate locatedNear P294 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: [Newby Hall, locatedNear, River Ure]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Ure
Context triple: [Newby Hall, locatedNear, 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 Mein
    River Mein is a small river in Dumfries and Galloway in southwest Scotland, flowing near the village of Ecclefechan.
  • E. 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.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3aa210ef88190be74bd60d7144953 completed April 18, 2026, 3:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a51e69c08190a5bff74823df430c completed May 10, 2026, 3:32 p.m.
Created at: April 10, 2026, 5:21 a.m.