Triple
T23312014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Venetian |
E590609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Venetian language |
C7452
|
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: variety of Venetian language Context triple: [Central Venetian, instanceOf, variety of Venetian language]
-
A.
Venetian dialect
chosen
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.
-
B.
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.
-
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.
regional variety of Lombard
A regional variety of Lombard is a specific form of the Lombard language spoken in a particular geographic area, characterized by distinct phonological, lexical, and syntactic features.
-
E.
variety of Piedmontese
A variety of Piedmontese is a distinct form or dialect of the Piedmontese language characterized by unique phonological, lexical, or syntactic features associated with a particular geographic area or speech community.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.