Triple

T32785896
Position Surface form Disambiguated ID Type / Status
Subject Ryburn Valley E838496 entity
Predicate hasFeature P182 FINISHED
Object Ryburn Reservoir
Ryburn Reservoir is a man-made lake in West Yorkshire, England, known for supplying water to the region and providing a scenic setting for walking and outdoor recreation.
E2039291 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: Ryburn Reservoir | Statement: [Ryburn Valley, hasFeature, Ryburn Reservoir]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ryburn Reservoir
Triple: [Ryburn Valley, hasFeature, Ryburn Reservoir]
Generated description
Ryburn Reservoir is a man-made lake in West Yorkshire, England, known for supplying water to the region and providing a scenic setting for walking and outdoor recreation.

Provenance (5 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_69f3493b83f48190be335cd42465cecf completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6cd4e6cd48190b31dd141db9b5515 completed May 3, 2026, 4:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3525a2e090819086fcbc212ca820e5 completed June 19, 2026, 11:18 a.m.
NEDg Description generation batch_6a35269b33708190b57524f61a445006 completed June 19, 2026, 11:23 a.m.
NED2 Entity disambiguation (via description) batch_6a352766ac5c8190a15fb9939e4527e6 completed June 19, 2026, 11:26 a.m.
Created at: May 1, 2026, 1:14 a.m.