Triple
T2908771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transeurasian languages |
E63631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed language macro-family |
C8599
|
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 macro-family Context triple: [Transeurasian languages, instanceOf, proposed language macro-family]
-
A.
language family
A language family is a group of languages that have evolved from a common ancestral language and share systematic similarities in vocabulary, grammar, and sound patterns.
-
B.
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.
-
C.
Altaic language group (disputed)
chosen
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.
-
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 based on shared structural and lexical features often argued to result from areal contact rather than common ancestry.
-
E.
macrolanguage variety
A macrolanguage variety is a specific linguistic form or set of forms that functions as one distinguishable member within a broader macrolanguage encompassing multiple closely related or mutually recognized language varieties.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:11 p.m.