Triple
T38351428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeneize |
E1041694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italo-Dalmatian lect |
C19369
|
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: Italo-Dalmatian lect Context triple: [Zeneize, instanceOf, Italo-Dalmatian lect]
-
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.
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.
-
C.
Kajkavian
Kajkavian is a South Slavic dialect (often considered a dialect of Croatian) characterized by its use of the interrogative pronoun "kaj," distinct phonological and grammatical features, and a historical literary tradition.
-
D.
Italo-Dalmatian variety
chosen
An Italo-Dalmatian variety is a Romance language or dialect belonging to the Italo-Dalmatian branch, historically spoken in Italy and along the eastern Adriatic coast, characterized by features intermediate between Italo-Romance and Eastern Romance languages.
-
E.
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.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.