Triple
T22198124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolomite Ladin varieties |
E548600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ladin dialects |
C1401
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ladin dialects Context triple: [Dolomite Ladin varieties, instanceOf, Ladin dialects]
-
A.
Romansh dialect
A Romansh dialect is a regional variety of the Romansh language, characterized by distinct phonological, lexical, and grammatical features specific to particular communities in southeastern Switzerland.
-
B.
Emilian-Romagnol dialect
Emilian-Romagnol dialect is a group of closely related Gallo-Italic varieties spoken in the Emilia-Romagna region of northern Italy, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard Italian and neighboring dialects.
-
C.
Alpine language
chosen
Alpine language is a conceptual class representing any linguistic system that has evolved within or is predominantly used in mountainous Alpine regions, shaped by their geography, culture, and historical isolation.
-
D.
Goral dialect
Goral dialect is a group of closely related Slavic vernaculars spoken by the Goral people in the mountainous regions along the Polish-Slovak border, characterized by features of Polish, Slovak, and other neighboring languages.
-
E.
Venetian dialect
Venetian dialect is a Romance language variety spoken primarily in the Veneto region of Italy, characterized by its distinct phonology, vocabulary, and grammar that set it apart from standard Italian.
- F. None of above.
Provenance (1 batch)
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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.