Triple
T7212341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kunigami language |
E149435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Ryukyuan language |
C7366
|
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: Northern Ryukyuan language Context triple: [Kunigami language, instanceOf, Northern Ryukyuan language]
-
A.
Chuukic language
The Chuukic language is a group of closely related Micronesian languages spoken primarily in the Chuuk State of the Federated States of Micronesia and surrounding regions, characterized by shared phonological and grammatical features within the Oceanic branch of the Austronesian language family.
-
B.
Formosan language
A Formosan language is any of the indigenous Austronesian languages spoken by the native peoples of Taiwan, distinct from but historically related to other Austronesian languages.
-
C.
Southern Wakashan language
A Southern Wakashan language is a member of the southern branch of the Wakashan language family, traditionally spoken by Indigenous peoples of the Pacific Northwest Coast, particularly on Vancouver Island and adjacent mainland areas.
-
D.
Japonic languages
chosen
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.
Kansai dialect
Kansai dialect is a group of Japanese dialects spoken in the Kansai region, characterized by distinctive pronunciation, vocabulary, and intonation often associated with humor and friendliness.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:53 p.m.