Triple

T7056962
Position Surface form Disambiguated ID Type / Status
Subject Glienicker Lake E164116 entity
Predicate partOf P40 FINISHED
Object Havel waterway E30026 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: Havel waterway | Statement: [Glienicker Lake, partOf, Havel waterway]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Havel waterway
Context triple: [Glienicker Lake, partOf, Havel waterway]
  • A. Oder–Havel Canal
    The Oder–Havel Canal is a major German waterway that links the Havel and Oder river systems, forming part of an important inland shipping route between Berlin and Poland.
  • B. Ružinovský canal
    Ružinovský canal is a man-made waterway in the Ružinov district of Bratislava, Slovakia, serving local drainage, recreation, and urban landscape functions.
  • C. Havel River chosen
    The Havel River is a major waterway in northeastern Germany that flows through Berlin and Brandenburg, connecting numerous lakes and serving as an important route for transport and recreation.
  • D. Elbe–Havel Canal
    The Elbe–Havel Canal is a major German waterway that links the Elbe and Havel river systems, forming part of an important east–west inland shipping route.
  • E. Britz Canal
    The Britz Canal is a short industrial waterway in Berlin, Germany, linking local waterways and serving as part of the city’s inland shipping network.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c68861678881909961ddf4d779f750 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e26a130c81908bdad15f5c4ae15d completed March 27, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7944809348190bfc96df73f1363b3 completed March 28, 2026, 8:41 a.m.
Created at: March 27, 2026, 2:38 p.m.