Triple

T20219976
Position Surface form Disambiguated ID Type / Status
Subject Battle of Günzburg E495225 entity
Predicate location P40 FINISHED
Object Günzburg 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: Günzburg | Statement: [Battle of Günzburg, location, Günzburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Günzburg
Context triple: [Battle of Günzburg, location, Günzburg]
  • A. Günzburg chosen
    Günzburg is a small Bavarian town in southern Germany, historically notable as the birthplace of Nazi physician Josef Mengele.
  • B. Kaufbeuren
    Kaufbeuren is a historic Bavarian town in southern Germany known for its well-preserved medieval old town and traditional Swabian culture.
  • C. Eichstätt
    Eichstätt is a historic Bavarian town in southern Germany known for its baroque architecture, Catholic university, and location within the Altmühltal Nature Park.
  • D. 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.
  • E. Haßfurt
    Haßfurt is a small town in northern Bavaria, Germany, situated on the Main River and known for its historic architecture and regional administrative role.
  • 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_69da626cff80819097b530718a7c98b6 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66edc88148190b003b72eb4c69da5 completed April 20, 2026, 6:22 p.m.
Created at: April 11, 2026, 11:39 p.m.