Triple

T20644866
Position Surface form Disambiguated ID Type / Status
Subject Gmunden District E507327 entity
Predicate containsMunicipality P852 FINISHED
Object Ohlsdorf 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: Ohlsdorf | Statement: [Gmunden District, containsMunicipality, Ohlsdorf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ohlsdorf
Context triple: [Gmunden District, containsMunicipality, Ohlsdorf]
  • A. Ohlsdorf chosen
    Ohlsdorf is a municipality in Austria’s Salzkammergut region, known for its cultural heritage and scenic Alpine surroundings.
  • B. Ohlsdorf, Hamburg
    Ohlsdorf, Hamburg is a northern district of Hamburg, Germany, best known for containing one of the world’s largest rural cemeteries, Ohlsdorf Cemetery.
  • C. Lippendorf
    Lippendorf is a village in Saxony, Germany, historically notable as the birthplace of Katharina von Bora, the wife of Martin Luther.
  • D. Olbrich
    Olbrich is a German surname most notably associated with architect Joseph Maria Olbrich, a key figure of the Vienna Secession movement.
  • E. Olsberg
    Olsberg is a small town in the Hochsauerland region of North Rhine-Westphalia, Germany, known for its scenic location in the Sauerland hills and outdoor recreation opportunities.
  • 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_69e0b4be702c8190a3d2410a881d310a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6af1d0be481909e090193dcfd9cf6 completed April 20, 2026, 10:56 p.m.
Created at: April 16, 2026, 11:43 a.m.