Triple

T17929043
Position Surface form Disambiguated ID Type / Status
Subject Gransee E448278 entity
Predicate district P2709 FINISHED
Object Oberhavel 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: Oberhavel | Statement: [Gransee, district, Oberhavel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oberhavel
Context triple: [Gransee, district, Oberhavel]
  • A. Oberhavel (district) chosen
    Oberhavel is a rural district in the German state of Brandenburg, known for its lakes, forests, and proximity to northern Berlin.
  • B. Luhe-Wildenau
    Luhe-Wildenau is a municipality in the district of Neustadt an der Waldnaab in the Upper Palatinate region of Bavaria, Germany.
  • C. Nordharz
    Nordharz is a municipality in the Harz region of Saxony-Anhalt, Germany, known for its proximity to the Harz Mountains and its blend of rural landscapes and small-town settlements.
  • D. Havelland
    Havelland is a rural district in western Brandenburg, Germany, known for its river landscapes along the Havel, historic towns, and agricultural character.
  • E. Niederschöneweide
    Niederschöneweide is a locality in the Berlin borough of Treptow-Köpenick, known for its riverside setting along the Spree and its mix of residential areas and former industrial sites.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a5511a408190973cf5fa1f286a26 completed April 19, 2026, 9:50 a.m.
Created at: April 10, 2026, 10:20 a.m.