Triple
T16583510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shexian dialect |
E402895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Huizhou Chinese variety |
C38055
|
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: Huizhou Chinese variety Context triple: [Shexian dialect, instanceOf, Huizhou Chinese variety]
-
A.
Southern Min variety
A Southern Min variety is a regional form of the Southern Min (Minnan) branch of Chinese, encompassing mutually related but often not mutually intelligible dialects spoken primarily in southern Fujian, eastern Guangdong, Hainan, Taiwan, and among overseas Chinese communities.
-
B.
variety of Hokkien
A variety of Hokkien is a regional or social dialect of the Hokkien Chinese language distinguished by its unique phonological, lexical, and syntactic features shaped by local history and contact with other languages.
-
C.
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.
-
D.
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.
-
E.
Southern Luo language
Southern Luo language is a group of closely related Nilotic languages spoken primarily around Lake Victoria in Kenya, Tanzania, and Uganda, known for their shared grammatical structures and mutual intelligibility.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.