Triple

T14676038
Position Surface form Disambiguated ID Type / Status
Subject Higher Hodder Bridge E344648 entity
Predicate hasView P854 FINISHED
Object River Hodder valley E68443 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 Hodder valley | Statement: [Higher Hodder Bridge, hasView, River Hodder valley]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Hodder valley
Context triple: [Higher Hodder Bridge, hasView, River Hodder valley]
  • A. River Hodder chosen
    River Hodder is a river in Lancashire, England, known for flowing through the Forest of Bowland and joining the River Ribble near Great Mitton.
  • B. Ager River
    The Ager River is a watercourse in Upper Austria that flows through the Salzkammergut region and ultimately joins the Traun River.
  • C. Lez River
    The Lez River is a short coastal river in southern France that flows through the city of Montpellier before emptying into the Mediterranean Sea.
  • D. River Ivel
    The River Ivel is a river in Bedfordshire, England, that flows northward through towns such as Biggleswade and Sandy before joining the River Great Ouse.
  • E. River Lud
    The River Lud is a small river in Lincolnshire, England, that flows through the market town of Louth before joining the River Witham system.
  • 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_69d822e283fc8190a0e4c235cf880052 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb5666e648190b5faa07076f497b8 completed April 14, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fedd1de868819084d71f75210d14f5 completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 1:27 a.m.