Triple

T6871248
Position Surface form Disambiguated ID Type / Status
Subject Hohe Tauern E158550 entity
Predicate locatedIn P40 FINISHED
Object Salzburg E19756 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: Salzburg | Statement: [Hohe Tauern, locatedIn, Salzburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salzburg
Context triple: [Hohe Tauern, locatedIn, Salzburg]
  • A. Salzburg chosen
    Salzburg is a historic Austrian city on the Salzach River, renowned for its baroque architecture, Alpine setting, and as the birthplace of composer Wolfgang Amadeus Mozart.
  • B. Innsbruck
    Innsbruck is a city in western Austria known for its Alpine setting and winter sports facilities, and it later successfully hosted the Winter Olympics in 1964 and 1976.
  • C. Linz
    Linz is a major Austrian city known for its industrial heritage, vibrant cultural scene, and location along the Danube River.
  • D. Klagenfurt
    Klagenfurt is the capital city of the Austrian state of Carinthia, known for its historic old town and proximity to Lake Wörthersee.
  • E. Gmunden
    Gmunden is a picturesque town in Upper Austria known for its lakeside setting on the Traunsee and its historic ceramics industry.
  • 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_69c68831e3648190a643c328122e4d43 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d8ac04e08190aa8011c0ade9d509 completed March 27, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7511ada2481909491b8f9bd3ead91 completed March 28, 2026, 3:55 a.m.
Created at: March 27, 2026, 2:22 p.m.