Triple

T11795068
Position Surface form Disambiguated ID Type / Status
Subject Ribble catchment E280484 entity
Predicate containsRiver P165 FINISHED
Object River Loud E81432 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 Loud | Statement: [Ribble catchment, containsRiver, River Loud]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Loud
Context triple: [Ribble catchment, containsRiver, River Loud]
  • A. River Loud chosen
    River Loud is a small river in Lancashire, England, that flows through rural countryside before joining the River Ribble.
  • B. River Brun
    River Brun is a small river in Lancashire, England, that flows through the town of Burnley and contributes to its local landscape and waterways.
  • C. River Kinder
    The River Kinder is a small moorland river in the Peak District of England, known for its dramatic Kinder Downfall waterfall and rugged upland scenery.
  • D. River Brit
    The River Brit is a small river in West Dorset, England, that flows through the town of Bridport before reaching the English Channel at West Bay.
  • E. River Lyd
    The River Lyd is a river in Devon, England, known for flowing through Lydford Gorge before joining the River Tamar.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a082d08190a42541396a06ed98 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f49cbc6808819094a73b505907e2ef completed May 1, 2026, 12:29 p.m.
Created at: April 8, 2026, 9:42 p.m.