Triple

T4634724
Position Surface form Disambiguated ID Type / Status
Subject Elde E101500 entity
Predicate mouthLocation P417 FINISHED
Object Dömitz E482832 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: Dömitz | Statement: [Elde, mouthLocation, Dömitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dömitz
Context triple: [Elde, mouthLocation, Dömitz]
  • A. Dömitz chosen
    Dömitz is a small historic town in northern Germany, known for its well-preserved fortress and location on the Elbe River near the former inner-German border.
  • B. Zinnowitz
    Zinnowitz is a seaside resort town on Germany’s Baltic Sea coast, known for its sandy beaches, historic spa architecture, and tourism on the island of Usedom.
  • C. Drensteinfurt
    Drensteinfurt is a small town in North Rhine-Westphalia, Germany, known for its historic architecture and location in the Münsterland region.
  • D. Prenzlau
    Prenzlau is a historic town in northeastern Germany’s Brandenburg region, known for its medieval architecture and role as a regional administrative center.
  • E. Lusatian Neisse
    The Lusatian Neisse is a river in Central Europe that flows through the Czech Republic, Germany, and Poland, forming part of the German–Polish border.
  • 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_69bd43d2f1c081908cd4b7ec48ecc73d completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a5ec8108190aeb1147a67bff057 completed March 20, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69be89c2485881908797f4a3560a0b04 completed March 21, 2026, 12:06 p.m.
Created at: March 20, 2026, 1:13 p.m.