Triple
T24798016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lolobi dialect |
E620442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Siwu language |
C49563
|
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: regional variety of Siwu language Context triple: [Lolobi dialect, instanceOf, regional variety of Siwu language]
-
A.
regional variety of Yue Chinese
A regional variety of Yue Chinese is a localized form of the Yue branch of Sinitic languages, characterized by distinct phonological, lexical, and syntactic features specific to a particular geographic area.
-
B.
regional variety of Jingpo language
A regional variety of the Jingpo language is a geographically or socially distinct form of Jingpo characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Jingpo varieties.
-
C.
Yao language variety
A Yao language variety is a specific regional or social form of the Yao language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Yao linguistic continuum.
-
D.
Zhuang language variety
A Zhuang language variety is a specific regional or social form of the Zhuang language, characterized by distinct phonological, lexical, and grammatical features within the broader Tai language continuum.
-
E.
regional variety of Mandar language
A regional variety of Mandar language is a localized form of the Mandar language distinguished by unique phonological, lexical, and sometimes grammatical features associated with a specific geographic area or community.
- F. None of above. chosen
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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:48 a.m.