Triple
T5563970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuscan dialect |
E145834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional dialect of Italian |
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: regional dialect of Italian Context triple: [Tuscan dialect, instanceOf, regional dialect of Italian]
-
A.
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.
-
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.
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.
-
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.
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.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:36 p.m.