Triple

T17820882
Position Surface form Disambiguated ID Type / Status
Subject Langer See E444977 entity
Predicate partOf P40 FINISHED
Object Dahme river system — NE NERFINISHED

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: Dahme river system | Statement: [Langer See, partOf, Dahme river system]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Dahme river system
Context triple: [Langer See, partOf, Dahme river system]
  • A. Dahme
    Dahme is a small coastal town on the Baltic Sea in northern Germany, known for its beaches and seaside tourism.
  • B. Dahme chosen
    The Dahme is a river in eastern Germany that flows through Brandenburg and Berlin before joining the Spree.
  • C. Spree–Dahme waterway
    The Spree–Dahme waterway is a network of interconnected rivers, lakes, and canals in Berlin and Brandenburg that forms an important inland navigation route and recreational water area in eastern Germany.
  • D. River Spree
    River Spree is a major river flowing through Berlin, Germany, known for shaping the city’s landscape and passing many historic and cultural landmarks.
  • E. Schwarmstedt’s Meiße River
    Schwarmstedt’s Meiße River is a small tributary watercourse in Lower Saxony, Germany, that flows into the Aller River near the town of Schwarmstedt.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48910eb8881908db8ec08e2752d7d completed April 19, 2026, 7:49 a.m.
Created at: April 10, 2026, 10:15 a.m.