Triple

T18128326
Position Surface form Disambiguated ID Type / Status
Subject Weißenburg-Gunzenhausen E433941 entity
Predicate contains P35 FINISHED
Object Gunzenhausen 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: Gunzenhausen | Statement: [Weißenburg-Gunzenhausen, contains, Gunzenhausen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gunzenhausen
Context triple: [Weißenburg-Gunzenhausen, contains, Gunzenhausen]
  • A. Gunzenhausen chosen
    Gunzenhausen is a historic town in Bavaria, Germany, known for its location on the Altmühl River and as a gateway to the Franconian Lake District.
  • B. Balzhausen
    Balzhausen is a small municipality in the Bavarian region of Swabia in southern Germany.
  • C. Gunzesried
    Gunzesried is a small village in the Bavarian Alps of Germany, known for its picturesque mountain scenery and traditional alpine character.
  • D. Walzenhausen
    Walzenhausen is a Swiss village and municipality in the canton of Appenzell Ausserrhoden, known for its scenic location above Lake Constance and views over the Rhine Valley.
  • E. Helmarshausen
    Helmarshausen is a historic district of the spa town Bad Karlshafen in northern Hesse, Germany, known for its medieval heritage and former Benedictine monastery.
  • 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddf061b48190b67356f1c266b80a completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:29 a.m.