Triple

T21996267
Position Surface form Disambiguated ID Type / Status
Subject Bezirk Cottbus E543213 entity
Predicate contains P35 FINISHED
Object Spremberg 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: Spremberg | Statement: [Bezirk Cottbus, contains, Spremberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spremberg
Context triple: [Bezirk Cottbus, contains, Spremberg]
  • A. Spremberg chosen
    Spremberg is a small town in eastern Germany’s Lusatia region, known for its location along the River Spree and its historic town center.
  • B. Presberg
    Presberg is a small district of the town Rüdesheim am Rhein in the Rheingau region of Hesse, Germany, known for its scenic location above the Rhine and surrounding vineyards and forests.
  • C. Jesberg
    Jesberg is a small municipality in the German state of Hesse, known for its rural setting and proximity to the Kellerwald-Edersee National Park.
  • D. Mösseberg
    Mösseberg is a plateau mountain and recreational area in Västergötland, Sweden, known for its nature reserve, outdoor activities, and scenic views near the town of Falköping.
  • E. Himberg
    Himberg is a small subdistrict within the Aegidienberg area of Bad Honnef in North Rhine-Westphalia, Germany.
  • 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.