Triple
T15543220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brescian |
E370534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lombard language variety |
C22310
|
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: Lombard language variety Context triple: [Brescian, instanceOf, Lombard language variety]
-
A.
regional variety of the Piedmontese language
A regional variety of the Piedmontese language is a geographically localized form of Piedmontese characterized by distinct phonological, lexical, and sometimes syntactic features shared by speakers in a specific area.
-
B.
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.
-
C.
Italian dialect
chosen
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.
-
D.
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.
-
E.
Gondi language variety
A Gondi language variety is a specific regional or social form of the Gondi language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Dravidian language continuum.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:07 a.m.