Triple

T21313066
Position Surface form Disambiguated ID Type / Status
Subject Oder-Spree E525393 entity
Predicate adminCenter P3892 FINISHED
Object Beeskow 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: Beeskow | Statement: [Oder-Spree, adminCenter, Beeskow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beeskow
Context triple: [Oder-Spree, adminCenter, Beeskow]
  • A. Beeskow chosen
    Beeskow is a small historic town in eastern Brandenburg, Germany, known for its medieval castle and role as a local cultural and administrative center.
  • B. Teterow
    Teterow is a small historic town in northeastern Germany known for its medieval architecture and location in the Mecklenburg Lake District.
  • C. Fürstenwalde
    Fürstenwalde is a town in eastern Germany’s Brandenburg region, known for its location on the River Spree and its historic churches and medieval architecture.
  • D. Elsterwerda
    Elsterwerda is a small town in the state of Brandenburg in eastern Germany, known for its regional railway connections and location near the Elbe-Elster district.
  • E. Pasewalk
    Pasewalk is a small historic town in northeastern Germany, located in the state of Mecklenburg-Vorpommern near the Polish border.
  • 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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75dcc6350819093763632b7e6e4ac completed April 21, 2026, 11:21 a.m.
Created at: April 16, 2026, 4:25 p.m.