Triple

T32383572
Position Surface form Disambiguated ID Type / Status
Subject Changdu Gan E827485 entity
Predicate instanceOf P0 FINISHED
Object regional variety of Gan Chinese C57925 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: regional variety of Gan Chinese
Context triple: [Changdu Gan, instanceOf, regional variety of Gan Chinese]
  • A. Gan Chinese variety chosen
    Gan Chinese variety is a group of closely related Sinitic dialects spoken primarily in Jiangxi province and neighboring regions, characterized by distinct phonology, vocabulary, and grammar that differentiate it from Mandarin and other Chinese varieties.
  • B. regional variety of Yue Chinese
    A regional variety of Yue Chinese is a localized form of the Yue branch of Sinitic languages, characterized by distinct phonological, lexical, and syntactic features specific to a particular geographic area.
  • C. regional variety of Siwu language
    A regional variety of the Siwu language is a geographically and socially distinct form of Siwu characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Siwu-speaking areas.
  • D. variety of Mandarin Chinese
    A variety of Mandarin Chinese is a regional or social form of the Mandarin language distinguished by its phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with other Mandarin forms.
  • E. 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.
  • 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_69f349177ddc8190ab0583f05597056b completed April 30, 2026, 12:20 p.m.
Created at: May 1, 2026, 12:51 a.m.