Triple
T2562589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandarin phonology |
E57275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of Mandarin Chinese |
C2298
|
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: component of Mandarin Chinese Context triple: [Mandarin phonology, instanceOf, component of Mandarin Chinese]
-
A.
variety of Mandarin Chinese
chosen
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.
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.
-
C.
Chinese language variety
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.
-
D.
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.
-
E.
Hmong-Mien language
A Hmong-Mien language is a member of a small family of tonal languages spoken primarily in southern China and Southeast Asia, characterized by complex phonology and rich systems of classifiers.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.