Triple

T2087424
Position Surface form Disambiguated ID Type / Status
Subject Berchtesgaden E45384 entity
Predicate locatedNear P294 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: [Berchtesgaden, locatedNear, Salzburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salzburg
Context triple: [Berchtesgaden, locatedNear, 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. Baden bei Wien
    Baden bei Wien is a historic spa town in eastern Austria renowned for its thermal springs, Biedermeier architecture, and proximity to Vienna.
  • E. St. Pölten
    St. Pölten is the capital city of the Austrian state of Lower Austria, known for its baroque architecture and role as a regional administrative and cultural center.
  • 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_69a8891869c88190a02643e3bb746f59 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abba5641208190b925676b8d80f300 completed March 7, 2026, 5:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae71aa1374819095bdad8291ac41a1 completed March 9, 2026, 7:07 a.m.
Created at: March 4, 2026, 7:41 p.m.