Triple

T22940551
Position Surface form Disambiguated ID Type / Status
Subject Hörsching E569714 entity
Predicate hasOfficialName P66 FINISHED
Object Hörsching 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: Hörsching | Statement: [Hörsching, hasOfficialName, Hörsching]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hörsching
Context triple: [Hörsching, hasOfficialName, Hörsching]
  • A. Hörsching chosen
    Hörsching is a municipality in Upper Austria, best known for hosting Linz Airport and lying near the city of Linz.
  • B. Kirchanschöring
    Kirchanschöring is a small Bavarian municipality in southeastern Germany, known for its rural character and scenic location near the Austrian border.
  • C. Geiselhöring
    Geiselhöring is a small town in Lower Bavaria, Germany, known for its rural character and location within the Straubing-Bogen district.
  • D. Ötigheim
    Ötigheim is a small municipality in southwestern Germany’s Baden-Württemberg state, known for its open-air theater and rural character within the Rastatt district.
  • E. Obergriesbach
    Obergriesbach is a small municipality in the district of Aichach-Friedberg in the Bavarian region of Germany.
  • 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_69e24590862c8190858f180ad302adab completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1813844b88190b05d3829b0c423c4 completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:45 p.m.