Triple

T23334242
Position Surface form Disambiguated ID Type / Status
Subject River Laver E591531 entity
Predicate hasName P744 FINISHED
Object River Laver — 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 Laver | Statement: [River Laver, hasName, River Laver]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: River Laver
Context triple: [River Laver, hasName, River Laver]
  • A. River Laver
    River Laver is a small river in North Yorkshire, England, that flows through the countryside near the city of Ripon before joining the River Skell.
  • B. River Laver
    The River Laver is a small river in North Yorkshire, England, that flows through rural landscapes before joining the River Nidd.
  • C. River Laver chosen
    River Laver is a small river in North Yorkshire, England, that flows through rural landscapes before joining the River Ure.
  • D. River Roden
    River Roden is a small river in Shropshire, England, that flows through rural countryside before joining the River Tern.
  • E. River Lossie
    The River Lossie is a river in northeast Scotland that flows through the town of Elgin before emptying into the Moray Firth.
  • 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.