Triple

T18264260
Position Surface form Disambiguated ID Type / Status
Subject Vechigen E437440 entity
Predicate neighboringMunicipality P17964 FINISHED
Object Oberburg 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: Oberburg | Statement: [Vechigen, neighboringMunicipality, Oberburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oberburg
Context triple: [Vechigen, neighboringMunicipality, Oberburg]
  • A. Oberburg chosen
    Oberburg is a municipality in the Emmental administrative district of the canton of Bern in Switzerland.
  • B. Obernbreit
    Obernbreit is a small municipality in the Kitzingen district of Bavaria, Germany, known for its rural Franconian character and wine-growing traditions.
  • C. Oberaudorf
    Oberaudorf is a small Bavarian town in southern Germany near the Austrian border, known for its alpine scenery and ski tourism.
  • D. Oberhöchstadt
    Oberhöchstadt is a district of the town of Kronberg im Taunus in Hesse, Germany, known for its residential character within the Taunus region.
  • E. Oberdrauburg
    Oberdrauburg is a market town in the Austrian state of Carinthia, situated in the upper Drava Valley near the border with East Tyrol.
  • 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_69d8b913351c8190932b6a426de04b41 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ff78b188819081da8e1d389c6c79 completed April 19, 2026, 4:14 p.m.
Created at: April 10, 2026, 10:34 a.m.