Triple

T11311816
Position Surface form Disambiguated ID Type / Status
Subject Dené–Yeniseian languages E267854 entity
Predicate instanceOf P0 FINISHED
Object hypothesized language family 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: hypothesized language family
Context triple: [Dené–Yeniseian languages, instanceOf, hypothesized language family]
  • 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. 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.
  • C. 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.
  • 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. hypothesis in historical linguistics
    A hypothesis in historical linguistics is a proposed explanation of how and why specific linguistic features or relationships between languages have changed over time, formulated to be tested against comparative and historical evidence.
  • 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_69d6aaca5c24819083db46a30d86cb34 completed April 8, 2026, 7:21 p.m.
Created at: April 8, 2026, 9:32 p.m.