Triple
T18588417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuzhou dialect |
E454297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Min dialect |
C40930
|
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: Eastern Min dialect Context triple: [Fuzhou dialect, instanceOf, Eastern Min dialect]
-
A.
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.
-
B.
Unami dialect
The Unami dialect is a historical variety of the Lenape (Delaware) language traditionally spoken by the Unami division of the Lenape people in parts of what are now Pennsylvania, New Jersey, and Delaware.
-
C.
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.
-
D.
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.
-
E.
Oshiwambo dialect
Oshiwambo dialect is a regional linguistic variety of the Oshiwambo language, characterized by distinct phonological, lexical, and grammatical features used by specific communities in northern Namibia and southern Angola.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.