Triple
T7624389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reggiano |
E172588
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Emilian-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: Emilian-Romagnol dialect Context triple: [Reggiano, instanceOf, Emilian-Romagnol dialect]
-
A.
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.
-
B.
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.
-
C.
Romansh dialect
A Romansh dialect is a regional variety of the Romansh language, characterized by distinct phonological, lexical, and grammatical features specific to particular communities in southeastern Switzerland.
-
D.
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.
-
E.
Alpine language
Alpine language is a conceptual class representing any linguistic system that has evolved within or is predominantly used in mountainous Alpine regions, shaped by their geography, culture, and historical isolation.
- F. None of above. chosen
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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:56 p.m.