Triple

T8882976
Position Surface form Disambiguated ID Type / Status
Subject Tiroler Achen E211454 entity
Predicate hasGermanName P1435 FINISHED
Object Tiroler Achen E211454 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: Tiroler Achen | Statement: [Tiroler Achen, hasGermanName, Tiroler Achen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tiroler Achen
Context triple: [Tiroler Achen, hasGermanName, Tiroler Achen]
  • A. Tiroler Achen chosen
    Tiroler Achen is a river flowing from the Austrian Tyrol through Bavaria and is one of the main tributaries feeding Germany’s Chiemsee lake.
  • B. Ötztaler Ache
    Ötztaler Ache is a fast-flowing alpine river in Tyrol, Austria, known for draining the Ötztal valley and offering popular whitewater rafting and kayaking routes.
  • C. Gasteiner Ache
    Gasteiner Ache is a mountain river in the Austrian Alps that flows through the Gastein Valley before joining the Salzach River.
  • D. Eisack
    Eisack is a major river in northern Italy that flows through the South Tyrol region, including the city of Bolzano, before joining the Adige.
  • E. Bregenzer Ach
    Bregenzer Ach is a river in western Austria that flows through the state of Vorarlberg before joining the Rhine.
  • 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_69ca838f9e20819096ab1f236a70381a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc616a01f48190b8bbde0e898a38c7 completed April 1, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfba1809dc81909776f1268cae9004 completed April 3, 2026, 1:01 p.m.
Created at: March 30, 2026, 6:53 p.m.