Triple

T22851368
Position Surface form Disambiguated ID Type / Status
Subject Northern Ryukyuan language E566363 entity
Predicate instanceOf P0 FINISHED
Object branch of Ryukyuan languages C7366 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: branch of Ryukyuan languages
Context triple: [Northern Ryukyuan language, instanceOf, branch of Ryukyuan languages]
  • A. Japonic languages chosen
    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.
  • B. branch of Austroasiatic languages
    A branch of Austroasiatic languages is a subgroup within the Austroasiatic language family whose member languages share a common historical origin and distinctive linguistic features.
  • C. Kuki-Chin language
    A Kuki-Chin language is a member of a subgroup of the Tibeto-Burman language family spoken primarily in northeastern India, Myanmar, and Bangladesh by various Kuki-Chin ethnic communities, characterized by complex phonology and verb morphology.
  • D. Formosan language
    A Formosan language is any of the indigenous Austronesian languages spoken by the native peoples of Taiwan, distinct from but historically related to other Austronesian languages.
  • E. Tai-Kadai language
    A Tai-Kadai language is a member of a family of tonal languages spoken primarily in Southeast Asia and southern China, characterized by similar phonological, lexical, and grammatical features that suggest a common historical origin.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
Created at: April 17, 2026, 3:36 p.m.