Triple

T21141744
Position Surface form Disambiguated ID Type / Status
Subject Glenesk E520947 entity
Predicate hasRiver P165 FINISHED
Object River North Esk — 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 North Esk | Statement: [Glenesk, hasRiver, River North Esk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: River North Esk
Context triple: [Glenesk, hasRiver, River North Esk]
  • A. River North Esk
    River North Esk is a river in Midlothian, Scotland, that flows through the town of Penicuik before joining the River Esk system.
  • B. River North Esk chosen
    River North Esk is a river in eastern Scotland that flows through Angus and Aberdeenshire before entering the North Sea.
  • C. River South Esk
    River South Esk is a Scottish river flowing through the county of Angus from the Grampian Mountains to the North Sea at Montrose.
  • D. River Eske
    River Eske is a short river in County Donegal, Ireland, flowing from Lough Eske through Donegal Town before entering Donegal Bay.
  • E. River Ryburn
    River Ryburn is a river in West Yorkshire, England, that flows through the Ryburn Valley and joins the River Calder near the town of Sowerby Bridge.
  • 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_69e0b50c6a848190a4e525a77a319b8a completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e723f96cf081909d10309e08aeca93 completed April 21, 2026, 7:15 a.m.
Created at: April 16, 2026, 2:57 p.m.