Triple

T10968501
Position Surface form Disambiguated ID Type / Status
Subject Waldeck-Frankenberg E259169 entity
Predicate capital P234 FINISHED
Object Korbach E289018 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: Korbach | Statement: [Waldeck-Frankenberg, capital, Korbach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korbach
Context triple: [Waldeck-Frankenberg, capital, Korbach]
  • A. Korbach chosen
    Korbach is a historic town in the German state of Hesse, known as the district seat of Waldeck-Frankenberg and for its well-preserved medieval old town.
  • B. Schambach
    Schambach is a small river in Bavaria, Germany, that flows into the Altmühl as one of its tributaries.
  • C. Weiterstadt
    Weiterstadt is a town in the German state of Hesse, located near Darmstadt and known for its residential areas and commercial centers.
  • D. Borgholzhausen
    Borgholzhausen is a small town in North Rhine-Westphalia, Germany, known for its location on the Teutoburg Forest and its historical ties to the former County of Ravensberg.
  • E. Kulmbach
    Kulmbach is a historic Bavarian town in northern Germany renowned for its beer brewing tradition and its hilltop Plassenburg Castle.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7719800388190943a0bffa48a2731 completed April 9, 2026, 9:30 a.m.
NED1 Entity disambiguation (via context triple) batch_69e344a2130081908d9d22ee84890925 completed April 18, 2026, 8:45 a.m.
Created at: April 8, 2026, 9:24 p.m.