Triple

T18283675
Position Surface form Disambiguated ID Type / Status
Subject Seddinsee E437924 entity
Predicate belongsToCategory P87 FINISHED
Object Inland waterways of Berlin NE NERFINISHED

How this triple was built (3 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: Inland waterways of Berlin | Statement: [Seddinsee, belongsToCategory, Inland waterways of Berlin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inland waterways of Berlin
Context triple: [Seddinsee, belongsToCategory, Inland waterways of Berlin]
  • A. Berlin waterway network
    The Berlin waterway network is an interconnected system of rivers, canals, and lakes that forms a major transport and recreational infrastructure throughout the German capital.
  • B. Berlin–Brandenburg waterway network
    The Berlin–Brandenburg waterway network is an extensive interconnected system of rivers, canals, and lakes in and around Berlin and Brandenburg that supports regional transport, recreation, and water management.
  • C. Berlin-Spandauer Schifffahrtskanal
    Berlin-Spandauer Schifffahrtskanal is a major canal in Berlin that connects the River Spree with the River Havel, serving as an important inland waterway for the city.
  • D. 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.
  • E. Stadtkanal Brandenburg
    Stadtkanal Brandenburg is a historic inner-city canal in Brandenburg an der Havel, Germany, that forms part of the town’s traditional waterway network and urban landscape.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Inland waterways of Berlin
Target entity description: The inland waterways of Berlin comprise the interconnected network of rivers, canals, and lakes that support the city’s transport, recreation, and water management.
  • A. Berlin waterway network chosen
    The Berlin waterway network is an interconnected system of rivers, canals, and lakes that forms a major transport and recreational infrastructure throughout the German capital.
  • B. Berlin–Brandenburg waterway network
    The Berlin–Brandenburg waterway network is an extensive interconnected system of rivers, canals, and lakes in and around Berlin and Brandenburg that supports regional transport, recreation, and water management.
  • C. Berlin-Spandauer Schifffahrtskanal
    Berlin-Spandauer Schifffahrtskanal is a major canal in Berlin that connects the River Spree with the River Havel, serving as an important inland waterway for the city.
  • D. 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.
  • E. Stadtkanal Brandenburg
    Stadtkanal Brandenburg is a historic inner-city canal in Brandenburg an der Havel, Germany, that forms part of the town’s traditional waterway network and urban landscape.
  • F. None of above.

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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e500f7ff088190933bb8f403ce7f9c completed April 19, 2026, 4:21 p.m.
Created at: April 10, 2026, 10:35 a.m.