Triple
T22197691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emilian dialects |
E548589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italo-Western Romance varieties |
C5912
|
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-Western Romance varieties Context triple: [Emilian dialects, instanceOf, Italo-Western Romance varieties]
-
A.
Romance language variety
chosen
A Romance language variety is a specific form or dialect of a Romance language, distinguished by its unique phonological, grammatical, and lexical features within the broader Romance language family.
-
B.
Italo-Dalmatian variety
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.
-
C.
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.
-
D.
para-Romani variety
A para-Romani variety is a mixed language in which Romani-derived vocabulary is embedded into the grammatical structure of a surrounding majority language, typically used as an in-group code by Romani or Romani-associated communities.
-
E.
Italian dialect
An Italian dialect is a regional or local variety of the Italian language, characterized by distinct phonological, lexical, and grammatical features shaped by historical, cultural, and geographic influences.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.