Triple

T16970635
Position Surface form Disambiguated ID Type / Status
Subject Bemerton E411664 entity
Predicate hasRiverNearby P8567 FINISHED
Object River Nadder E357428 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 Nadder | Statement: [Bemerton, hasRiverNearby, River Nadder]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Nadder
Context triple: [Bemerton, hasRiverNearby, River Nadder]
  • A. River Nadder chosen
    The River Nadder is a chalk stream in Wiltshire, England, that flows through the countryside to join the River Avon at Salisbury.
  • B. 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.
  • C. River Clettwr
    River Clettwr is a small river in west Wales that flows through Ceredigion before joining the River Teifi.
  • D. River Soar
    The River Soar is a major river in central England that flows through Leicestershire and the city of Leicester before joining the River Trent.
  • E. 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.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0ac23a48190992fa125fceb1eb2 completed April 18, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012eccd1e48190aa0dc64562d6ff1f completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:31 a.m.