Triple

T31891938
Position Surface form Disambiguated ID Type / Status
Subject Wuhle Valley E814167 entity
Predicate partOf P40 FINISHED
Object Wuhle River basin
The Wuhle River basin is the drainage area surrounding the Wuhle River in Berlin and Brandenburg, Germany, encompassing its valleys, tributaries, and associated landscapes.
E1984849 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: Wuhle River basin | Statement: [Wuhle Valley, partOf, Wuhle River basin]
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: Wuhle River basin
Triple: [Wuhle Valley, partOf, Wuhle River basin]
Generated description
The Wuhle River basin is the drainage area surrounding the Wuhle River in Berlin and Brandenburg, Germany, encompassing its valleys, tributaries, and associated landscapes.

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_69f348ef817481908440e2250319bcc8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b158cc5c81909ce5b32c9a97ae72 completed May 3, 2026, 2:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2e8a2c75348190900832da5f8803e9 completed June 14, 2026, 11:02 a.m.
NEDg Description generation batch_6a2e8b0d7b9881909941c614281a6c05 completed June 14, 2026, 11:05 a.m.
NED2 Entity disambiguation (via description) batch_6a2e8c005eb48190a28f4f07ad7c70af completed June 14, 2026, 11:09 a.m.
Created at: April 30, 2026, 11:58 p.m.