Triple

T11768627
Position Surface form Disambiguated ID Type / Status
Subject Traunsee E279839 entity
Predicate hasLakesideTown P59883 FINISHED
Object Traunkirchen E921202 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: Traunkirchen | Statement: [Traunsee, hasLakesideTown, Traunkirchen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Traunkirchen
Context triple: [Traunsee, hasLakesideTown, Traunkirchen]
  • A. Traunkirchen chosen
    Traunkirchen is a picturesque lakeside village in Upper Austria, known for its scenic setting on Lake Traunsee and historic pilgrimage church.
  • B. Traiskirchen
    Traiskirchen is a town in Lower Austria best known internationally for hosting one of Austria’s largest refugee reception centers.
  • C. Amstetten
    Amstetten is a town in northeastern Austria that serves as an important regional transport and commercial hub between Linz and Vienna.
  • D. Gumpoldskirchen
    Gumpoldskirchen is a historic wine-growing town in Lower Austria, renowned for its traditional vineyards and picturesque setting near Vienna.
  • E. Mitterskirchen
    Mitterskirchen is a small municipality in the district of Rottal-Inn in Lower Bavaria, Germany, known for its rural character and traditional Bavarian setting.
  • 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_69d6ab01d2688190ad8ed6bda487eaa5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a526979c8190ad2089997906855b completed April 10, 2026, 7:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69f684c71548819081af6734b8b7279a completed May 2, 2026, 11:12 p.m.
Created at: April 8, 2026, 9:41 p.m.