Triple

T22734968
Position Surface form Disambiguated ID Type / Status
Subject River Wiske E562240 entity
Predicate hasName P744 FINISHED
Object River Wiske — 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 Wiske | Statement: [River Wiske, hasName, River Wiske]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: River Wiske
Context triple: [River Wiske, hasName, River Wiske]
  • A. River Wiske chosen
    River Wiske is a small river in North Yorkshire, England, that flows through rural landscapes and villages before joining the River Swale.
  • B. Colne River
    The Colne River is a tributary of the River Thames in southern England that has historically marked parts of the boundary of Middlesex and neighboring counties.
  • C. River Ribble
    The River Ribble is a major river in northern England that flows through North Yorkshire and Lancashire before emptying into the Irish Sea near Preston.
  • D. River Gaunless
    River Gaunless is a small river in County Durham, England, that flows through former coal-mining areas before joining the River Wear.
  • E. River Weaver
    The River Weaver is a river in Cheshire, England, historically important for salt transport and navigation, that flows northward to join the River Mersey.
  • 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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1796f030881908e141564d442bd1b completed April 29, 2026, 3:22 a.m.
Created at: April 17, 2026, 3:22 p.m.