Triple

T20043595
Position Surface form Disambiguated ID Type / Status
Subject Rastatt district E497493 entity
Predicate contains P35 FINISHED
Object Gernsbach 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: Gernsbach | Statement: [Rastatt district, contains, Gernsbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gernsbach
Context triple: [Rastatt district, contains, Gernsbach]
  • A. Gernsbach chosen
    Gernsbach is a historic town in southwestern Germany’s Black Forest region, known for its medieval old town and picturesque setting along the Murg River.
  • B. Emsbach
    Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
  • C. Miesbach
    Miesbach is a historic town in southern Germany known for its traditional Bavarian culture and picturesque Alpine foothill setting.
  • D. Grünbach
    Grünbach is a small stream in Germany that serves as a tributary of the river Jagst.
  • E. Pfaffenweiler
    Pfaffenweiler is a small municipality in southwestern Germany’s Baden-Württemberg region, situated near Freiburg im Breisgau and known for its winegrowing and picturesque Black Forest surroundings.
  • 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_69da627278c88190babe4297a9df1236 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e662ed59bc8190a9ff25493e500ebb completed April 20, 2026, 5:31 p.m.
Created at: April 11, 2026, 3:37 p.m.