Triple

T27547082
Position Surface form Disambiguated ID Type / Status
Subject Askham Bridge E695390 entity
Predicate isInWatercourseValley P162693 FINISHED
Object River Lowther valley LITERAL 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 Lowther valley | Statement: [Askham Bridge, isInWatercourseValley, River Lowther valley]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInWatercourseValley
Context triple: [Askham Bridge, isInWatercourseValley, River Lowther valley]
  • A. isOnWatercourse
    Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
  • B. hasPositionInWatercourse
    Indicates that one entity occupies a specific location or position within the course of a body of water.
  • C. hasWatercourseType
    Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
  • D. isNaturalWatercourse
    Indicates that one entity is a naturally formed flowing body of water (such as a river or stream), rather than an artificial or man-made channel.
  • E. isWatercourseOf
    Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
  • F. None of above. chosen

Provenance (4 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_69ef5386c3e08190bfe33aa326e1f72b completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62f850d148190929315018576b731 completed May 2, 2026, 5:08 p.m.
PD Predicate disambiguation batch_69f62c1762f881908c25e8f70ecd5041 completed May 2, 2026, 4:53 p.m.
PDg Predicate description generation batch_69f62cd1912c8190ab3f3288442115a4 completed May 2, 2026, 4:56 p.m.
Created at: April 27, 2026, 1:33 p.m.