Triple

T33289562
Position Surface form Disambiguated ID Type / Status
Subject Stocksbridge E852276 entity
Predicate hasReservoirNearby P17985 FINISHED
Object Underbank Reservoir
Underbank Reservoir is a man-made lake in South Yorkshire, England, used for water supply, recreation, and wildlife habitat near the town of Stocksbridge.
E2074566 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: Underbank Reservoir | Statement: [Stocksbridge, hasReservoirNearby, Underbank 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: Underbank Reservoir
Triple: [Stocksbridge, hasReservoirNearby, Underbank Reservoir]
Generated description
Underbank Reservoir is a man-made lake in South Yorkshire, England, used for water supply, recreation, and wildlife habitat near the town of Stocksbridge.

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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6de76e05881908a6eee3fc1f10c9f completed May 3, 2026, 5:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3689b30af88190a8b18eb2a9117c5b completed June 20, 2026, 12:38 p.m.
NEDg Description generation batch_6a368a1f9b7881909ae68762eda61568 completed June 20, 2026, 12:39 p.m.
NED2 Entity disambiguation (via description) batch_6a368aa45db881908d6ede9e654754d1 completed June 20, 2026, 12:42 p.m.
Created at: May 1, 2026, 1:32 a.m.