Triple
T31324946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occitan (in Guardia Piemontese) |
E798857
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Occitan variety |
C5911
|
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: Occitan variety Context triple: [Occitan (in Guardia Piemontese), instanceOf, Occitan variety]
-
A.
Occitan dialect
chosen
An Occitan dialect is a regional variety of the Occitan language, characterized by distinct phonological, lexical, and grammatical features shaped by local history and geography within southern France and neighboring areas.
-
B.
Franco-Provençal dialect
A Franco-Provençal dialect is a regional variety of the Gallo-Romance language continuum spoken primarily in parts of France, Switzerland, and Italy, characterized by features distinct from both standard French and Occitan.
-
C.
regional variety of the Catalan language
A regional variety of the Catalan language is a geographically defined form of Catalan characterized by distinct phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Catalan varieties.
-
D.
Occitan orthography
Occitan orthography is the standardized system of writing the Occitan language, encompassing its spelling rules, accentuation, and regional variants used across southern France and neighboring areas.
-
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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.