Triple

T34121023
Position Surface form Disambiguated ID Type / Status
Subject Neuhaus (Möhnesee) E875130 entity
Predicate locatedNear P294 FINISHED
Object Möhnesee Reservoir
Möhnesee Reservoir is a large artificial lake in North Rhine-Westphalia, Germany, known for its historic dam and role as a major recreational and water management area in the region.
E2084495 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: Möhnesee Reservoir | Statement: [Neuhaus (Möhnesee), locatedNear, Möhnesee 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: Möhnesee Reservoir
Triple: [Neuhaus (Möhnesee), locatedNear, Möhnesee Reservoir]
Generated description
Möhnesee Reservoir is a large artificial lake in North Rhine-Westphalia, Germany, known for its historic dam and role as a major recreational and water management area in the region.

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_69f349a9271c81909576994c9ef7b179 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70f407fe88190a75a102d68573a2d completed May 3, 2026, 9:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36c1c0ec00819093687486e2aca859 completed June 20, 2026, 4:37 p.m.
NEDg Description generation batch_6a36c23c390c8190816a96a7acdc84a4 completed June 20, 2026, 4:39 p.m.
NED2 Entity disambiguation (via description) batch_6a36c37508a88190b76ae2d93eb748a0 completed June 20, 2026, 4:44 p.m.
Created at: May 1, 2026, 1:53 a.m.