Triple
T27355789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phrae Pwo Karen |
E685681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Pwo Karen |
C52750
|
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 Pwo Karen Context triple: [Phrae Pwo Karen, instanceOf, regional variety of Pwo Karen]
-
A.
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.
-
B.
regional variety of the Kayan language
A regional variety of the Kayan language is a geographically distinct form of Kayan characterized by unique phonological, lexical, or grammatical features shared by speakers in a particular area.
-
C.
variety of Sgaw Karen language
A variety of Sgaw Karen language is a regional or social form of the Sgaw Karen language distinguished by unique phonological, lexical, or grammatical features within the broader Sgaw Karen-speaking community.
-
D.
Kaili language variety
The Kaili language variety is a group of closely related Austronesian dialects spoken primarily in Central Sulawesi, Indonesia, characterized by shared grammatical structures but notable phonological and lexical differences between communities.
-
E.
regional variety of Ghomalaʼ
A regional variety of Ghomalaʼ is a geographically localized dialect of the Ghomalaʼ language characterized by distinct phonological, lexical, or syntactic features specific to a particular 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:51 a.m.