Triple

T17463578
Position Surface form Disambiguated ID Type / Status
Subject Zehlendorf E425218 entity
Predicate near P350 FINISHED
Object Wannsee 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: Wannsee | Statement: [Zehlendorf, near, Wannsee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wannsee
Context triple: [Zehlendorf, near, Wannsee]
  • A. Wannsee chosen
    Wannsee is a lakeside district in southwestern Berlin, Germany, known for its villa colonies, recreational waterfront, and as the site of the infamous 1942 Wannsee Conference.
  • B. Kaufering
    Kaufering is a municipality in Bavaria, Germany, known historically for its World War II subcamps of Dachau and its location near the town of Landsberg am Lech.
  • C. Pulhof
    Pulhof is a residential neighborhood in the Antwerp district of Berchem, Belgium, known for its quiet streets and urban character.
  • D. Beelitz
    Beelitz is a small German town in the state of Brandenburg, best known for its historic asparagus cultivation and the nearby Beelitz-Heilstätten sanatorium complex.
  • E. Neubukow
    Neubukow is a small town in northern Germany best known as the birthplace of archaeologist Heinrich Schliemann.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451a5bba08190b61a21fa7538ed69 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.