Triple
T18567366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Fujian dialects |
E453789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of Sinitic language varieties |
C5354
|
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: group of Sinitic language varieties Context triple: [Southern Fujian dialects, instanceOf, group of Sinitic language varieties]
-
A.
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.
-
B.
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.
-
C.
group of language varieties
A group of language varieties is a conceptual class encompassing related dialects, sociolects, or registers that share a common linguistic base but differ in systematic ways across regions, communities, or contexts.
-
D.
variety of Shina language
A variety of the Shina language is a regional or social dialect of Shina distinguished by its unique phonological, lexical, or grammatical features while remaining mutually intelligible to varying degrees with other Shina dialects.
-
E.
group of dialects
chosen
A group of dialects is a set of closely related language varieties that share common structural features and a historical or geographic connection within a larger language.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.