Triple
T31443918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haikou Hainanese |
E802139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Hainanese |
C26674
|
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 Hainanese Context triple: [Haikou Hainanese, instanceOf, regional variety of Hainanese]
-
A.
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.
-
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.
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.
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.
-
E.
Southern Min variety
chosen
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.
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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:08 p.m.