Triple

T33098088
Position Surface form Disambiguated ID Type / Status
Subject Shaoyang Old Xiang E846965 entity
Predicate instanceOf P0 FINISHED
Object Old Xiang dialect C58681 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: Old Xiang dialect
Context triple: [Shaoyang Old Xiang, instanceOf, Old Xiang dialect]
  • A. Old Xiang dialect chosen
    Old Xiang dialect is a conservative branch of the Xiang group of Chinese dialects, primarily spoken in central Hunan province, that preserves many archaic phonological and lexical features lost in other modern Chinese varieties.
  • B. Hakka dialect
    Hakka dialect is a group of closely related Sinitic varieties spoken primarily by the Hakka people, characterized by distinct phonology, vocabulary, and grammar that set it apart from Mandarin, Cantonese, and other Chinese dialects.
  • C. Eastern Min dialect
    The Eastern Min dialect is a branch of the Min Chinese language group spoken primarily in eastern Fujian province, characterized by significant phonological and lexical differences from Mandarin and other Chinese dialects.
  • D. Kaili dialect
    The Kaili dialect is a regional variety of the Kaili language spoken in Central Sulawesi, Indonesia, characterized by distinct phonological, lexical, and grammatical features that differentiate it from other local Austronesian languages and dialects.
  • E. Jin Chinese dialect
    Jin Chinese dialect is a group of closely related Sinitic varieties spoken primarily in Shanxi and surrounding regions, often considered distinct from Mandarin due to its unique phonological and lexical features.
  • 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_69f3495590dc8190aa04f3dec74ce976 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:26 a.m.