Triple
T23554655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinzenberg dialect |
E578149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Sutsilvan Romansh |
C18428
|
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: regional variety of Sutsilvan Romansh Context triple: [Heinzenberg dialect, instanceOf, regional variety of Sutsilvan Romansh]
-
A.
Romansh dialect
chosen
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.
Ladin dialect group
The Ladin dialect group comprises closely related Rhaeto-Romance varieties spoken primarily in the Dolomite mountain region of northern Italy, characterized by shared phonological and lexical features distinct from neighboring Romance languages.
-
C.
variety of the Ladin language
A variety of the Ladin language is a regional or local form of Ladin distinguished by its own phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Ladin varieties.
-
D.
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.
-
E.
Isnag dialect
The Isnag dialect is a variant of the Isnag language spoken by the Isnag people of northern Luzon in the Philippines, characterized by its distinct phonology, vocabulary, and grammatical features within the Northern Luzon language group.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:12 p.m.