Triple

T21996264
Position Surface form Disambiguated ID Type / Status
Subject Bezirk Cottbus E543213 entity
Predicate contains P35 FINISHED
Object Herzberg (Elster) 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: Herzberg (Elster) | Statement: [Bezirk Cottbus, contains, Herzberg (Elster)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Herzberg (Elster)
Context triple: [Bezirk Cottbus, contains, Herzberg (Elster)]
  • A. Herzberg (Elster) chosen
    Herzberg (Elster) is a small town in the state of Brandenburg in eastern Germany, known for its historic architecture and location along the Black Elster river.
  • B. Wülknitz
    Wülknitz is a small municipality in the German state of Saxony that forms part of the broader Leipzig metropolitan area.
  • C. Irschenberg
    Irschenberg is a Bavarian municipality in southern Germany known for its scenic location in the Alpine foothills and its prominent motorway ascent on the A8 between Munich and Salzburg.
  • D. Stechow-Ferchesar
    Stechow-Ferchesar is a small rural municipality in the Havelland district of Brandenburg, Germany.
  • E. Löcknitz
    Löcknitz is a river in eastern Germany that flows through Brandenburg and is associated with the town of Erkner.
  • 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_69e11e2c814c8190837d072789000486 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12765fb0c81908f7b7acda065ee2f completed April 28, 2026, 9:32 p.m.
Created at: April 16, 2026, 8:19 p.m.