Triple
T26455216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergamasque |
E665465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gallo-Italic dialect |
C5232
|
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: Gallo-Italic dialect Context triple: [Bergamasque, instanceOf, Gallo-Italic dialect]
-
A.
Gallo-Italic language
chosen
A Gallo-Italic language is a member of a group of Romance languages spoken primarily in northern Italy and parts of Switzerland, characterized by features intermediate between Gallo-Romance (like French) and Italo-Romance (like standard Italian).
-
B.
Ligurian dialect
Ligurian dialect is a Romance language variety spoken primarily in the Liguria region of northwestern Italy and nearby areas, characterized by its own phonological, lexical, and grammatical features distinct from standard Italian.
-
C.
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.
-
D.
Sardinian dialect
Sardinian dialect is a regional variety of the Sardinian language, characterized by distinct phonetic, lexical, and grammatical features that vary across different areas of the island of Sardinia.
-
E.
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.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:08 a.m.