Triple
T5704719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italo-Dalmatian languages |
E125756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romance language branch |
C15284
|
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: Romance language branch Context triple: [Italo-Dalmatian languages, instanceOf, Romance language branch]
-
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.
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.
-
C.
Italic language branch
chosen
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.
-
D.
Indo-European language branch
The Indo-European language branch is a major subgroup within the Indo-European language family comprising closely related languages that share a common ancestral origin and distinctive linguistic features.
-
E.
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).
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:45 p.m.