Triple
T32920242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Hsiang |
E842124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Xiang Chinese variety |
C58017
|
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: Xiang Chinese variety Context triple: [Old Hsiang, instanceOf, Xiang Chinese variety]
-
A.
Wu Chinese variety
A Wu Chinese variety is a regional form of the Wu branch of Sinitic languages, characterized by shared phonological, lexical, and grammatical features distinct from other Chinese varieties.
-
B.
Huizhou Chinese variety
Huizhou Chinese variety is a group of closely related Sinitic lects spoken in southern Anhui and nearby regions, characterized by significant phonological and lexical divergence from Mandarin and other major Chinese varieties.
-
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.
variety of Shina language
A variety of the Shina language is a regional or social dialect of Shina distinguished by its unique phonological, lexical, or grammatical features while remaining mutually intelligible to varying degrees with other Shina dialects.
-
E.
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.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.