Triple

T12917312
Position Surface form Disambiguated ID Type / Status
Subject Bad Tölz-Wolfratshausen E309018 entity
Predicate borderedBy P224 FINISHED
Object Miesbach E282753 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: Miesbach | Statement: [Bad Tölz-Wolfratshausen, borderedBy, Miesbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Miesbach
Context triple: [Bad Tölz-Wolfratshausen, borderedBy, Miesbach]
  • A. Miesbach chosen
    Miesbach is a historic town in southern Germany known for its traditional Bavarian culture and picturesque Alpine foothill setting.
  • B. Biberach an der Riß
    Biberach an der Riß is a historic town in the German state of Baden-Württemberg, known for its well-preserved medieval old town and traditional Swabian culture.
  • C. Gernsbach
    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.
  • D. Lautlingen
    Lautlingen is a village in the Zollernalb district of Baden-Württemberg, Germany, now incorporated as a district of the town of Albstadt.
  • E. Emsbach
    Emsbach is a small river in Germany that flows through Hesse before joining the Lahn.
  • 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_69d7bdf92b588190acdf2a2291ac4590 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d971a1e8088190af697629baecf59f completed April 10, 2026, 9:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8a9a12008190a86d8e11bf86d536 completed May 8, 2026, 7:02 a.m.
Created at: April 9, 2026, 5:41 p.m.