Triple

T19057541
Position Surface form Disambiguated ID Type / Status
Subject River Deerness E466436 entity
Predicate hasName P744 FINISHED
Object River Deerness — 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 Deerness | Statement: [River Deerness, hasName, River Deerness]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: River Deerness
Context triple: [River Deerness, hasName, River Deerness]
  • A. River Deerness chosen
    River Deerness is a small river in County Durham, England, that flows through the Deerness Valley before joining the River Wear.
  • B. River Nene
    River Nene is a major river in eastern England that flows through Northamptonshire, Cambridgeshire, and Norfolk before reaching The Wash on the North Sea.
  • C. Aar River
    The Aar River is a small river in western Germany that flows through the Taunus region and passes spa towns such as Bad Schwalbach before joining the Lahn.
  • D. River Lyde
    The River Lyde is a small river in Hampshire, England, that flows through rural landscapes before joining the River Loddon.
  • E. River Arun
    The River Arun is a major river in West Sussex, England, flowing from the South Downs to the English Channel and historically important for navigation and trade.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5dc0742288190a594be859184841a completed April 20, 2026, 7:55 a.m.
Created at: April 10, 2026, 12:03 p.m.