Triple
T3618477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Ischl |
E76662
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Traun |
E276375
|
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: Traun | Statement: [Bad Ischl, hasRiver, Traun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Traun Context triple: [Bad Ischl, hasRiver, Traun]
-
A.
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.
-
B.
Traunsee
Traunsee is a picturesque alpine lake in Upper Austria, known for its deep waters, surrounding mountains, and popular lakeside towns like Gmunden.
-
C.
Wiesener
Wiesener is a surname, likely of German origin, that serves as a variant spelling of the name Wiesner.
-
D.
Traun River
chosen
The Traun River is a major tributary of the Danube in Austria, flowing through the Salzkammergut lake district and the state of Upper Austria.
-
E.
Eisack
Eisack is a major river in northern Italy that flows through the South Tyrol region, including the city of Bolzano, before joining the Adige.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b72b3481909f4a09000d1815d9 |
completed | March 8, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4882d20fc819082c0b640cddce269 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:23 p.m.