Triple
T15587607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DFI – Romansh (Departament federal da l’intern) |
E374662
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romansh-language abbreviation |
C36376
|
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: Romansh-language abbreviation Context triple: [DFI – Romansh (Departament federal da l’intern), instanceOf, Romansh-language abbreviation]
-
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.
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.
-
C.
Luxembourgish exonym
A Luxembourgish exonym is the name used in the Luxembourgish language for a foreign place, region, or country that differs from the name used in the local or original language.
-
D.
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.
-
E.
Swiss canton code
A Swiss canton code is a standardized short alphanumeric identifier used to uniquely represent each canton within Switzerland for administrative, statistical, and legal purposes.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:11 a.m.