Triple
T32507979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinyu |
E830852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Jin Chinese |
C57926
|
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: variety of Jin Chinese Context triple: [Jinyu, instanceOf, variety of Jin Chinese]
-
A.
Jin Chinese variety
chosen
Jin Chinese variety is a group of closely related Sinitic dialects spoken primarily in Shanxi and surrounding regions of northern China, often considered distinct from Mandarin due to its unique phonological and lexical features.
-
B.
variety of Mandarin Chinese
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.
-
C.
Jin Chinese dialect
Jin Chinese dialect is a group of closely related Sinitic varieties spoken primarily in Shanxi and surrounding regions, often considered distinct from Mandarin due to its unique phonological and lexical features.
-
D.
Gan Chinese variety
Gan Chinese variety is a group of closely related Sinitic dialects spoken primarily in Jiangxi province and neighboring regions, characterized by distinct phonology, vocabulary, and grammar that differentiate it from Mandarin and other Chinese varieties.
-
E.
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.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.