Triple
T5386178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turinese Piedmontese |
E120204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italo‑Romance lect |
C2433
|
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‑Romance lect Context triple: [Turinese Piedmontese, instanceOf, Italo‑Romance lect]
-
A.
Gallo-Italic language
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.
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.
-
C.
Romance language variety
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.
-
D.
Romance lect
chosen
A Romance lect is a language variety—such as a dialect, sociolect, or closely related language—derived from Vulgar Latin and belonging to the Romance language family.
-
E.
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.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 2:03 p.m.