Triple

T9487412
Position Surface form Disambiguated ID Type / Status
Subject Traisen E228795 entity
Predicate hasNameInLanguage P15 FINISHED
Object Traisen (German) E228795 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: Traisen (German) | Statement: [Traisen, hasNameInLanguage, Traisen (German)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Traisen (German)
Context triple: [Traisen, hasNameInLanguage, Traisen (German)]
  • A. 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.
  • B. Traun
    Traun is a town in the Austrian state of Upper Austria, located near Linz along the Traun River and known as a residential and industrial suburb of the regional capital.
  • C. Traun
    Traun is a river in southeastern Germany that flows through the Chiemgau region of Bavaria.
  • D. Salzach River
    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.
  • E. Traisen chosen
    Traisen is a river in northeastern Austria that flows through Lower Austria before joining the Danube.
  • 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_69ca847424f081908180305555139f7a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd80c443b88190968d2092a73e1ee4 completed April 1, 2026, 8:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69d12d18fd908190b562fa0a8dad7c63 completed April 4, 2026, 3:24 p.m.
Created at: March 30, 2026, 7:55 p.m.