Triple

T11105106
Position Surface form Disambiguated ID Type / Status
Subject River Sett E262607 entity
Predicate hasTributary P415 FINISHED
Object River Kinder E172613 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 Kinder | Statement: [River Sett, hasTributary, River Kinder]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Kinder
Context triple: [River Sett, hasTributary, River Kinder]
  • A. River Kinder chosen
    The River Kinder is a small moorland river in the Peak District of England, known for its dramatic Kinder Downfall waterfall and rugged upland scenery.
  • B. 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.
  • C. River Brit
    The River Brit is a small river in West Dorset, England, that flows through the town of Bridport before reaching the English Channel at West Bay.
  • D. River Kemp
    River Kemp is a small river in Shropshire, England, known for flowing through rural countryside before joining the River Clun.
  • E. River Loud
    River Loud is a small river in Lancashire, England, that flows through rural countryside before joining the River Ribble.
  • 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79a2e319881909e66d3c0c73b56bc completed April 9, 2026, 12:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69e441c3b1788190868fae6919544149 completed April 19, 2026, 2:45 a.m.
Created at: April 8, 2026, 9:27 p.m.