Triple
T6496064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunda-Sulawesi languages |
E148163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed language group |
C14762
|
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: proposed language group Context triple: [Sunda-Sulawesi languages, instanceOf, proposed language group]
-
A.
hypothesized language group
chosen
A hypothesized language group is a proposed set of languages believed to share a common ancestor based on comparative evidence, but whose genetic relationship has not yet been conclusively demonstrated or widely accepted.
-
B.
areal language grouping
An areal language grouping is a set of languages that share structural features due to geographic proximity and contact rather than common genetic origin.
-
C.
group of language varieties
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.
-
D.
Altaic language group (disputed)
The Altaic language group (disputed) is a proposed but widely contested macro-family that would link Turkic, Mongolic, Tungusic, and sometimes Koreanic and Japonic languages under a common ancestral origin.
-
E.
Altaic language group (disputed)
The Altaic language group (disputed) is a proposed but widely contested macro-family that would link Turkic, Mongolic, Tungusic, and sometimes Koreanic and Japonic languages based on shared structural and lexical features often argued to result from areal contact rather than common ancestry.
- 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 4:53 p.m.