Triple

T8371869
Position Surface form Disambiguated ID Type / Status
Subject Scandoromani E197478 entity
Predicate instanceOf P0 FINISHED
Object para-Romani variety C23958 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: para-Romani variety
Context triple: [Scandoromani, instanceOf, para-Romani variety]
  • A. Vlach language
    The Vlach language is a Romance language or group of dialects spoken by Vlach communities in the Balkans, characterized by strong influence from surrounding Slavic, Greek, and Albanian languages.
  • B. 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.
  • C. 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.
  • D. Sarmatian language
    The Sarmatian language was an extinct Eastern Iranian language (or group of dialects) once spoken by the Sarmatian tribes of the Eurasian steppe, known primarily through onomastic and limited historical evidence.
  • E. 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.
  • F. None of above. chosen

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_69ca82f56730819080cec5d991c76f4c completed March 30, 2026, 2:04 p.m.
Created at: March 30, 2026, 6:01 p.m.