Triple

T6310758
Position Surface form Disambiguated ID Type / Status
Subject Ashbourne E141493 entity
Predicate locatedOn P40 FINISHED
Object River Henmore E430742 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 Henmore | Statement: [Ashbourne, locatedOn, River Henmore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Henmore
Context triple: [Ashbourne, locatedOn, River Henmore]
  • A. River Lednock
    River Lednock is a small Scottish river in Perth and Kinross that flows through Glen Lednock and the village of Comrie before joining the River Earn.
  • B. Henmore Brook chosen
    Henmore Brook is a small watercourse in Derbyshire, England, that flows through the town of Ashbourne before joining the River Dove.
  • C. River Hamps
    River Hamps is a small river in Staffordshire, England, known for flowing through the limestone landscapes of the Peak District before joining the River Dove.
  • D. River Wick
    River Wick is a small river in northern Scotland that flows through the town of Wick before entering the North Sea.
  • E. River Lostock
    River Lostock is a river in Lancashire, England, known for flowing through the Chorley area before joining the River Douglas.
  • 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_69c008d00efc8190a36c05b4b4a3bf4b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0648074b081908ba661651ba705a7 completed March 22, 2026, 9:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65fb7e7c88190bef0a15c12250b13 completed March 27, 2026, 10:45 a.m.
Created at: March 22, 2026, 4:28 p.m.