Triple

T20862236
Position Surface form Disambiguated ID Type / Status
Subject Teltow-Fläming E513648 entity
Predicate contains P35 FINISHED
Object Niederer Fläming 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: Niederer Fläming | Statement: [Teltow-Fläming, contains, Niederer Fläming]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Niederer Fläming
Context triple: [Teltow-Fläming, contains, Niederer Fläming]
  • A. Fläming chosen
    Fläming is a low mountain and heathland region in eastern Germany known for its forests, rolling hills, and historic towns.
  • B. Hohenfinow
    Hohenfinow is a small municipality in the Barnim district of the federal state of Brandenburg in northeastern Germany.
  • C. Prignitz
    Prignitz is a rural district in northwestern Brandenburg, Germany, known for its historic towns, agricultural landscapes, and location along the Elbe River.
  • D. Sachsenflur
    Sachsenflur is a district of the town Lauda-Königshofen in the Main-Tauber region of Baden-Württemberg, Germany.
  • E. Teltow
    Teltow is a town in the German state of Brandenburg, located just southwest of Berlin and known for its historical core and proximity to the capital.
  • 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3ad3d1c8190be2fe35a85f2447c completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 12:44 p.m.