Triple
T35619413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallesanese |
E1029269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Istriot dialect |
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: Istriot dialect Context triple: [Gallesanese, instanceOf, Istriot dialect]
-
A.
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.
-
B.
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.
-
C.
Goral dialect
Goral dialect is a group of closely related Slavic vernaculars spoken by the Goral people in the mountainous regions along the Polish-Slovak border, characterized by features of Polish, Slovak, and other neighboring languages.
-
D.
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.
-
E.
Isnag dialect
The Isnag dialect is a variant of the Isnag language spoken by the Isnag people of northern Luzon in the Philippines, characterized by its distinct phonology, vocabulary, and grammatical features within the Northern Luzon language group.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.