Triple

T9745837
Position Surface form Disambiguated ID Type / Status
Subject Main River region E236304 entity
Predicate containsCity P294 FINISHED
Object Kitzingen E315601 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: Kitzingen | Statement: [Main River region, containsCity, Kitzingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kitzingen
Context triple: [Main River region, containsCity, Kitzingen]
  • A. Kitzingen chosen
    Kitzingen is a historic town in northern Bavaria, Germany, known for its wine production and location along the Main River.
  • B. Günzburg
    Günzburg is a small Bavarian town in southern Germany, historically notable as the birthplace of Nazi physician Josef Mengele.
  • C. Wolfratshausen
    Wolfratshausen is a Bavarian town in southern Germany known for its historic old town, riverside setting on the Loisach and Isar, and proximity to Munich and the Alps.
  • D. Kulmbach
    Kulmbach is a historic Bavarian town in northern Germany renowned for its beer brewing tradition and its hilltop Plassenburg Castle.
  • E. Metzingen
    Metzingen is a town in the German state of Baden-Württemberg, known for its Swabian heritage and large outlet shopping district.
  • 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_69ca84d3e24481908a476e2231123cf9 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9f65ad788190b68d731b6f516d93 completed April 1, 2026, 10:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4f31e3d5c8190a044eaf67ebc9f08 completed April 19, 2026, 3:22 p.m.
Created at: March 30, 2026, 8:23 p.m.