Triple
T32448200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lvliang dialect |
E829203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jin Chinese dialect |
C58156
|
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: Jin Chinese dialect Context triple: [Lvliang dialect, instanceOf, Jin Chinese dialect]
-
A.
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.
-
B.
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.
-
C.
Hokkien dialect
Hokkien dialect is a group of Southern Min Chinese varieties spoken primarily in Taiwan, Fujian, and Southeast Asian Chinese communities, known for its rich tonal system and distinct vocabulary from Mandarin.
-
D.
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.
-
E.
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.
- F. None of above. chosen
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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:56 a.m.