Triple
T22835922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Piedmontese varieties |
E565946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gallo-Italic dialect group |
C5232
|
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: Gallo-Italic dialect group Context triple: [Eastern Piedmontese varieties, instanceOf, Gallo-Italic dialect group]
-
A.
Gallo-Italic language
chosen
A Gallo-Italic language is a member of a group of Romance languages spoken primarily in northern Italy and parts of Switzerland, characterized by features intermediate between Gallo-Romance (like French) and Italo-Romance (like standard Italian).
-
B.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
-
C.
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.
-
D.
Italic language branch
The Italic language branch is a subgroup of the Indo-European language family that includes Latin and its descendants (the Romance languages) as well as several extinct ancient languages once spoken on the Italian Peninsula.
-
E.
Roma subgroup
A Roma subgroup is a distinct community within the broader Romani people, defined by shared ancestry, dialect, cultural practices, and often historical migration patterns.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:35 p.m.