Triple

T18439015
Position Surface form Disambiguated ID Type / Status
Subject Marzahn-Hellersdorf E450473 entity
Predicate hasRiver P165 FINISHED
Object Wuhle 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: Wuhle | Statement: [Marzahn-Hellersdorf, hasRiver, Wuhle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wuhle
Context triple: [Marzahn-Hellersdorf, hasRiver, Wuhle]
  • A. Wuhle chosen
    Wuhle is a small river in Berlin, Germany, that flows through the eastern districts before joining the Spree.
  • B. Wiese River
    The Wiese River is a tributary of the Rhine flowing through parts of Germany and Switzerland, including the municipality of Riehen near Basel.
  • C. Wakenitz
    Wakenitz is a river in northern Germany that flows through the city of Lübeck and connects the Ratzeburger See to the Trave River.
  • D. Rüdnitz
    Rüdnitz is a small municipality in the Barnim district of the federal state of Brandenburg in northeastern Germany.
  • E. Saalach River
    The Saalach River is an Alpine river in Austria and Germany that flows through the spa town of Bad Reichenhall before joining the Salzach.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c0ed6708190ae90efd8455ec352 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:30 a.m.