Triple
T21843767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italo-Romance dialects |
E539321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of Romance language varieties |
C6018
|
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: group of Romance language varieties Context triple: [Italo-Romance dialects, instanceOf, group of Romance language varieties]
-
A.
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.
-
B.
group of language varieties
chosen
A group of language varieties is a conceptual class encompassing related dialects, sociolects, or registers that share a common linguistic base but differ in systematic ways across regions, communities, or contexts.
-
C.
group of dialects
A group of dialects is a set of closely related language varieties that share common structural features and a historical or geographic connection within a larger language.
-
D.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
-
E.
Slavic dialect grouping
A Slavic dialect grouping is a conceptual class that organizes related Slavic language varieties into clusters based on shared phonological, grammatical, and lexical features reflecting common historical development and geographic proximity.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:55 p.m.