Triple

T35363437
Position Surface form Disambiguated ID Type / Status
Subject Güntersberge E1021558 entity
Predicate hasLake P1025 FINISHED
Object Bergsee Güntersberge
Bergsee Güntersberge is a small scenic lake and recreational area near the town of Güntersberge in the Harz region of Germany, popular for swimming, boating, and nature tourism.
E2137545 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: Bergsee Güntersberge | Statement: [Güntersberge, hasLake, Bergsee Güntersberge]
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: Bergsee Güntersberge
Triple: [Güntersberge, hasLake, Bergsee Güntersberge]
Generated description
Bergsee Güntersberge is a small scenic lake and recreational area near the town of Güntersberge in the Harz region of Germany, popular for swimming, boating, and nature tourism.

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_69f76def44c881908a20e8008572eb44 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f791d039d48190802792bc81c7d10b completed May 3, 2026, 6:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3823dd42d481908486775704558de1 completed June 21, 2026, 5:48 p.m.
NEDg Description generation batch_6a3824d5a74c8190ae63ee78a409afd5 completed June 21, 2026, 5:52 p.m.
NED2 Entity disambiguation (via description) batch_6a3826b8a46c81909104152da09055b0 completed June 21, 2026, 6 p.m.
Created at: May 3, 2026, 4:03 p.m.