Triple

T19975972
Position Surface form Disambiguated ID Type / Status
Subject Ashover E493690 entity
Predicate hasRiver P165 FINISHED
Object River Amber — 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 Amber | Statement: [Ashover, hasRiver, River Amber]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: River Amber
Context triple: [Ashover, hasRiver, River Amber]
  • A. River Amber chosen
    The River Amber is a small river in Derbyshire, England, that flows through the Amber Valley before joining the River Derwent.
  • B. River Bourne
    River Bourne is a small river in Dorset, England, that flows through and gives its name to the coastal town of Bournemouth.
  • C. River Bourne
    River Bourne is a small river in Surrey, England, that flows through villages such as Chobham before joining the River Thames.
  • D. River Bourne
    River Bourne is a chalk stream in Wiltshire, England, that flows through the Bourne Valley before joining the River Avon near Salisbury.
  • E. River Bourne
    River Bourne is a small river in Kent, England, that serves as a tributary within the local drainage system and contributes to the region’s rural landscape and ecology.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65d0f4fb48190ad63afeff3513523 completed April 20, 2026, 5:06 p.m.
Created at: April 11, 2026, 3:26 p.m.