Triple

T21996263
Position Surface form Disambiguated ID Type / Status
Subject Bezirk Cottbus E543213 entity
Predicate contains P35 FINISHED
Object Guben 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: Guben | Statement: [Bezirk Cottbus, contains, Guben]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Guben
Context triple: [Bezirk Cottbus, contains, Guben]
  • A. Guben chosen
    Guben is a town in eastern Germany near the Polish border, historically part of Brandenburg and known for its textile and industrial heritage.
  • B. Gubāru
    Gubāru is an ancient Near Eastern figure, likely a Babylonian or Persian official known from cuneiform and classical sources in the context of the Achaemenid Empire.
  • C. Gubkin
    Gubkin is a mining-oriented city in western Russia known for its iron ore industry and location within Belgorod Oblast.
  • D. Gaub
    Gaub is a barangay (village-level administrative division) of the municipality of Oton in the province of Iloilo, Philippines.
  • E. Gubin
    Gubin is a town in western Poland situated on the Lusatian Neisse River, directly opposite the German town of Guben, forming a cross-border urban area.
  • 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.