Triple

T4847778
Position Surface form Disambiguated ID Type / Status
Subject Altstadt (Salzburg) E108333 entity
Predicate locatedOnRiver P165 FINISHED
Object Salzach E151401 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: Salzach | Statement: [Altstadt (Salzburg), locatedOnRiver, Salzach]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salzach
Context triple: [Altstadt (Salzburg), locatedOnRiver, Salzach]
  • A. Salzach River chosen
    The Salzach River is a major river in Austria and Germany that flows through the city of Salzburg and forms part of the border between the two countries.
  • B. Traisen
    Traisen is a river in northeastern Austria that flows through Lower Austria before joining the Danube.
  • C. Traun River
    The Traun River is a major tributary of the Danube in Austria, flowing through the Salzkammergut lake district and the state of Upper Austria.
  • D. Wertach River
    The Wertach River is a tributary waterway in Bavaria, Germany, flowing northward through towns such as Kaufbeuren and Augsburg before joining the Lech River.
  • E. Alte Donau
    Alte Donau is a former branch of the Danube River in Vienna that now serves as a popular recreational lake for swimming, boating, and waterside leisure.
  • 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_69bd4409b264819085ab855f3eb5381a completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d1aefdc8190910b78615730f991 completed March 20, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5cdafb3481908594ae883c6e9872 completed March 21, 2026, 8:54 a.m.
Created at: March 20, 2026, 1:25 p.m.