Triple
T10170813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penang Hokkien |
E235326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Min lect |
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: Southern Min lect Context triple: [Penang Hokkien, instanceOf, Southern Min lect]
-
A.
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.
-
B.
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.
-
C.
Formosan language
A Formosan language is any of the indigenous Austronesian languages spoken by the native peoples of Taiwan, distinct from but historically related to other Austronesian languages.
-
D.
Mon language
Mon language is an Austroasiatic language historically spoken by the Mon people of Myanmar and Thailand, notable for its ancient inscriptions and significant influence on the region’s scripts and cultures.
-
E.
Minahasan language
The Minahasan language is an Austronesian language (or group of closely related dialects) traditionally spoken by the Minahasan people of North Sulawesi, Indonesia, characterized by complex verbal morphology and significant influence from Malay/Indonesian.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:10 p.m.