Triple
T16584152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taizhou Wu |
E402909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Wu Chinese |
C7052
|
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 Wu Chinese Context triple: [Taizhou Wu, instanceOf, regional variety of Wu Chinese]
-
A.
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.
-
B.
Chinese language variety
chosen
A Chinese language variety is a distinct, historically rooted form of the Chinese language—such as Mandarin, Cantonese, or Shanghainese—characterized by its own phonology, vocabulary, and grammar, and often mutually unintelligible with other such forms.
-
C.
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.
-
D.
Sinitic language
A Sinitic language is any member of the Chinese branch of the Sino-Tibetan language family, characterized by tonal phonology, analytic grammar, and a shared historical connection to Classical Chinese.
-
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.
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.