Triple
T14482219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walser German dialects |
E359133
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Triesenberg |
E503251
|
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: Triesenberg | Statement: [Walser German dialects, spokenIn, Triesenberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Triesenberg Context triple: [Walser German dialects, spokenIn, Triesenberg]
-
A.
Triesenberg
chosen
Triesenberg is a mountainous municipality in Liechtenstein known for its traditional Walser culture and scenic alpine landscapes.
-
B.
Reinsberg
Reinsberg is a municipality in the German state of Saxony, located within the administrative district of Mittelsachsen.
-
C.
Geiersthal
Geiersthal is a small municipality in the Bavarian Forest region of southeastern Germany.
-
D.
Landensberg
Landensberg is a small municipality in the Bavarian region of southern Germany.
-
E.
Johannisberg
Johannisberg is a prominent peak in the Austrian Alps, located in the High Tauern range near the Grossglockner.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924bc548819087a2f693840d7426 |
completed | April 14, 2026, 7:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d8f1bf081908c37f8f41767b382 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:20 a.m.