Triple

T13911834
Position Surface form Disambiguated ID Type / Status
Subject Kleinmachnow E334515 entity
Predicate hasLandmark P105 FINISHED
Object Kleinmachnow lock E634280 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: Kleinmachnow lock | Statement: [Kleinmachnow, hasLandmark, Kleinmachnow lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kleinmachnow lock
Context triple: [Kleinmachnow, hasLandmark, Kleinmachnow lock]
  • A. Kleinmachnow lock chosen
    Kleinmachnow lock is a major lock complex near Berlin that regulates water levels and ship traffic on the Teltow Canal, serving as an important inland navigation structure in eastern Germany.
  • B. Wusterwitz Lock
    Wusterwitz Lock is a navigation lock on the Elbe–Havel Canal in Germany that regulates water levels and enables vessels to pass between different canal sections.
  • C. Hohenwarthe Lock
    Hohenwarthe Lock is a major navigation lock in Germany that helps vessels transition between different water levels on the Elbe–Havel Canal.
  • D. Charlottenburg Lock
    Charlottenburg Lock is a major navigation lock on Berlin’s River Spree that regulates water levels and enables ship traffic through the Charlottenburg district.
  • E. Elbe shipping lock
    The Elbe shipping lock is a key navigational structure on the Elbe River that enables vessels to bypass water level differences and safely transit near Lauenburg.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2723461881908376b5509ee0d530 completed April 14, 2026, 11:38 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c72879e48190ac01d0a2023b098c completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:16 p.m.