Triple
T26525503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bwe Karen language |
E670676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Karenic language |
C51703
|
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: Karenic language Context triple: [Bwe Karen language, instanceOf, Karenic language]
-
A.
Hurro-Urartian language
A Hurro-Urartian language is a member of an extinct family of ancient Near Eastern languages, primarily known from cuneiform inscriptions of the Hurrians and Urartians in the second and first millennia BCE.
-
B.
Tai-Kadai language
A Tai-Kadai language is a member of a family of tonal languages spoken primarily in Southeast Asia and southern China, characterized by similar phonological, lexical, and grammatical features that suggest a common historical origin.
-
C.
Caspian language
A Caspian language is any of several closely related Northwestern Iranian languages spoken along the southern coast of the Caspian Sea, characterized by shared phonological and grammatical features distinct from standard Persian.
-
D.
Kayanic language
A Kayanic language is a member of a subgroup of Austronesian languages spoken primarily by the Kayan, Kenyah, and related peoples of Borneo, characterized by shared phonological, lexical, and grammatical features distinct within the Greater North Borneo branch.
-
E.
Anatolian language
An Anatolian language is any member of an extinct branch of the Indo-European language family once spoken in ancient Anatolia (modern-day Turkey), including languages such as Hittite, Luwian, and Lycian.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:31 a.m.