Triple
T2054402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokkien language |
E45641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Min language |
C7051
|
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 language Context triple: [Hokkien language, instanceOf, Southern Min language]
-
A.
Tai language
A Tai language is a member of the Tai branch of the Kra–Dai language family, characterized by tonal phonology and analytic grammar, spoken primarily in Southeast Asia by Tai ethnic groups.
-
B.
Quechuan language
A Quechuan language is any member of a family of indigenous languages of the Andes, primarily spoken in Peru, Bolivia, Ecuador, Colombia, and Argentina, that share common grammatical structures and vocabulary derived from a Proto-Quechuan ancestor.
-
C.
Chibchan language
A Chibchan language is a member of a family of indigenous languages spoken primarily in Central America and northern South America, characterized by shared grammatical and phonological features reflecting a common ancestral origin.
-
D.
Sinitic language
chosen
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.
Central Luzon language
A Central Luzon language is a member of a subgroup of Philippine Austronesian languages spoken primarily in the Central Luzon region of the Philippines, characterized by shared phonological, grammatical, and lexical features distinct from other Philippine language groups.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:39 p.m.