Triple
T15205319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmunden |
E363373
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Traunsee |
E279839
|
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: Traunsee | Statement: [Gmunden, locatedOn, Traunsee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Traunsee Context triple: [Gmunden, locatedOn, Traunsee]
-
A.
Traunsee
chosen
Traunsee is a picturesque alpine lake in Upper Austria, known for its deep waters, surrounding mountains, and popular lakeside towns like Gmunden.
-
B.
Irrsee
Irrsee is a small, scenic lake in the Salzkammergut region of Upper Austria, known for its warm waters and tranquil natural setting.
-
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.
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.
-
E.
Traun
Traun is a river in southeastern Germany that flows through the Chiemgau region of Bavaria.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b7964c8190bc8dc3444b94f15e |
completed | April 15, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef687bdc819090ec8a4e1af9f422 |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:11 a.m.