Triple
T3955242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wu dialects |
E84960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sinitic language group |
C7052
|
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: Sinitic language group Context triple: [Wu dialects, instanceOf, Sinitic language group]
-
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.
Sino-Tibetan language
A Sino-Tibetan language is any member of a large language family, including Chinese and Tibeto-Burman languages, characterized by shared historical origins in East and Southeast Asia and often featuring tonal systems and analytic grammar.
-
C.
Chinese language variety
chosen
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.
Japonic languages
Japonic languages are a small language family native to Japan and nearby regions, including Japanese and the Ryukyuan languages, characterized by shared grammatical structures and historical origins.
-
E.
Austronesian language
An Austronesian language is any member of a large family of languages spoken from Madagascar across Island Southeast Asia and the Pacific to Easter Island, characterized by shared phonological, grammatical, and lexical features tracing back to a common ancestral tongue.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:30 p.m.