Triple
T18658777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabarchin |
E456135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ligurian language variety |
C16085
|
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: Ligurian language variety Context triple: [Tabarchin, instanceOf, Ligurian language variety]
-
A.
Ligurian dialect
chosen
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.
-
B.
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.
-
C.
Sardinian dialect
Sardinian dialect is a regional variety of the Sardinian language, characterized by distinct phonetic, lexical, and grammatical features that vary across different areas of the island of Sardinia.
-
D.
Emilian-Romagnol dialect
Emilian-Romagnol dialect is a group of closely related Gallo-Italic varieties spoken in the Emilia-Romagna region of northern Italy, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard Italian and neighboring dialects.
-
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.
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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.