Triple

T12420593
Position Surface form Disambiguated ID Type / Status
Subject Leverkusen E296756 entity
Predicate hasTwinTown P919 FINISHED
Object Schwedt E689416 NE FINISHED

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: Schwedt | Statement: [Leverkusen, hasTwinTown, Schwedt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schwedt
Context triple: [Leverkusen, hasTwinTown, Schwedt]
  • A. Schwedt chosen
    Schwedt is a town in northeastern Germany, located on the Oder River near the Polish border, known for its industrial facilities and cross-border regional ties.
  • B. Geringswalde
    Geringswalde is a small town in the Free State of Saxony in eastern Germany, known for its rural character and location within the Central Saxon region.
  • C. Wandlitz
    Wandlitz is a municipality in the German state of Brandenburg, known for its lakes, forests, and proximity to Berlin.
  • D. Zinnowitz
    Zinnowitz is a seaside resort town on Germany’s Baltic Sea coast, known for its sandy beaches, historic spa architecture, and tourism on the island of Usedom.
  • E. Riesa
    Riesa is a town in the German state of Saxony, situated on the Elbe River and known historically as an important regional railway and industrial center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d6efd748190a5d9396a343e41e1 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6cbb096d881908dfd2a7126632d96 completed May 3, 2026, 4:14 a.m.
Created at: April 8, 2026, 9:55 p.m.