Triple
T27091895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrarese dialect |
E686188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Emiliano-Romagnol dialect |
C22615
|
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: Emiliano-Romagnol dialect Context triple: [Ferrarese dialect, instanceOf, Emiliano-Romagnol dialect]
-
A.
Emilian-Romagnol dialect
chosen
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.
Italian dialect
An Italian dialect is a regional or local variety of the Italian language, characterized by distinct phonological, lexical, and grammatical features shaped by historical, cultural, and geographic influences.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:41 a.m.