Triple
T22371579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Ladin dialect group |
E553052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ladin dialect group |
C46178
|
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 dialect group Context triple: [Central Ladin dialect group, instanceOf, Ladin dialect group]
-
A.
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.
-
B.
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.
-
C.
Alpine language
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.
Slovene dialect group
A Slovene dialect group is a classification of closely related regional varieties of the Slovene language that share common phonological, morphological, syntactic, and lexical features.
-
E.
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.
- F. None of above. chosen
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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.