Triple

T22829191
Position Surface form Disambiguated ID Type / Status
Subject Karlsruhe district E565749 entity
Predicate borders P224 FINISHED
Object Landau in der Pfalz 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: Landau in der Pfalz | Statement: [Karlsruhe district, borders, Landau in der Pfalz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Landau in der Pfalz
Context triple: [Karlsruhe district, borders, Landau in der Pfalz]
  • A. Landau in der Pfalz chosen
    Landau in der Pfalz is a historic university and wine-producing city in Germany’s Rhineland-Palatinate region, known as a key center of the Southern Palatinate wine route.
  • B. Land of Hadeln
    The Land of Hadeln is a historic coastal region in northern Germany, known for its fertile marshlands, dike systems, and long-standing agricultural traditions along the lower Elbe.
  • C. Bad Schönborn
    Bad Schönborn is a German spa town in the state of Baden-Württemberg, known for its therapeutic thermal baths and health resorts.
  • D. Dinkelscherben
    Dinkelscherben is a municipality in the Swabian region of Bavaria in southern Germany.
  • E. Saal an der Saale
    Saal an der Saale is a small municipality in northern Bavaria, Germany, situated along the Franconian Saale River.
  • 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2a0e308190941064965346f890 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:34 p.m.