Triple

T1839094
Position Surface form Disambiguated ID Type / Status
Subject Main E41131 entity
Predicate hasCityOnBank P7935 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, hasCityOnBank, Kitzingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kitzingen
Context triple: [Main, hasCityOnBank, 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. Lampoldshausen
    Lampoldshausen is a German village best known as a major site for rocket propulsion research and testing facilities of the German Aerospace Center.
  • D. Markranstädt
    Markranstädt is a small town in the German state of Saxony, located near Leipzig and known for its local industry and proximity to the Kulkwitzer See recreation area.
  • E. Saalfeld
    Saalfeld is a town in the German state of Thuringia, known for its historic old town and former significance as a regional railway and industrial center.
  • 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_69a88647f9388190909bc36e795bdaec completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb03b3eb08190ae68d8476fc89c7f completed March 7, 2026, 4:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69b12dd43d248190b5918548c1b37a4e completed March 11, 2026, 8:54 a.m.
Created at: March 4, 2026, 7:33 p.m.