Triple

T20667833
Position Surface form Disambiguated ID Type / Status
Subject Freising district E507938 entity
Predicate locatedIn P40 FINISHED
Object Hallertau 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: Hallertau | Statement: [Freising district, locatedIn, Hallertau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hallertau
Context triple: [Freising district, locatedIn, Hallertau]
  • A. Saaz
    Saaz is the German name for the Czech town of Žatec, historically renowned as a major center of hop-growing and beer production.
  • B. Heffen
    Heffen is a village in the municipality of Mechelen in the Belgian province of Antwerp.
  • C. Hallertau hop-growing region chosen
    The Hallertau hop-growing region is a renowned agricultural area in Bavaria, Germany, famous as one of the world’s largest and oldest hop-producing regions for brewing beer.
  • D. Müller-Thurgau
    Müller-Thurgau is a white wine grape variety known for producing light, aromatic wines, particularly in cool-climate regions of Central Europe.
  • E. Bischofsmais
    Bischofsmais is a small Bavarian municipality in southeastern Germany known for its forested landscape and outdoor recreation in the Bavarian Forest region.
  • 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_69e0b4c059bc81908ea762cd73ea4424 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6b5c4c4608190ae17da4a59e5ae80 completed April 20, 2026, 11:24 p.m.
Created at: April 16, 2026, 11:44 a.m.