Triple

T15048284
Position Surface form Disambiguated ID Type / Status
Subject Mulde floodplain near Dessau E379288 entity
Predicate near P350 FINISHED
Object Dessau E102721 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: Dessau | Statement: [Mulde floodplain near Dessau, near, Dessau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dessau
Context triple: [Mulde floodplain near Dessau, near, Dessau]
  • A. Dessau chosen
    Dessau is a German city best known for its association with the Bauhaus movement and its iconic modernist architecture.
  • B. Oranienburg
    Oranienburg is a town in Brandenburg, Germany, historically known as the site of the Nazi Sachsenhausen concentration camp.
  • C. Degendorf
    Degendorf is a locality within the Bavarian town and district of Lichtenfels in Germany.
  • D. Sangerhausen
    Sangerhausen is a town in the German state of Saxony-Anhalt, known for its historic mining heritage and its renowned Europa-Rosarium rose garden.
  • E. Riedenburg
    Riedenburg is a small Bavarian town in southern Germany known for its scenic location in the Altmühl Valley and its historic castles.
  • 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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69deda8e64e48190873104a02a676ff3 completed April 15, 2026, 12:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69fee5e2b2188190b96807ca6442fb01 completed May 9, 2026, 7:44 a.m.
Created at: April 10, 2026, 3 a.m.