Triple
T1985143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabellic languages |
E43122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italic languages subgroup |
C4276
|
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: Italic languages subgroup Context triple: [Sabellic languages, instanceOf, Italic languages subgroup]
-
A.
language family subgroup
chosen
A language family subgroup is a set of closely related languages within a larger language family that share a more recent common ancestor and distinctive linguistic features.
-
B.
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).
-
C.
Berber language grouping
A Berber language grouping is a conceptual class that encompasses the related Afroasiatic languages spoken by Berber (Amazigh) peoples across North Africa, classified together based on shared historical, structural, and lexical features.
-
D.
Japonic languages
Japonic languages are a small language family native to Japan and nearby regions, including Japanese and the Ryukyuan languages, characterized by shared grammatical structures and historical origins.
-
E.
Dravidian language
A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.