Triple
T38514162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maututu dialect |
E921995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Nakanai language |
C66328
|
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 the Nakanai language Context triple: [Maututu dialect, instanceOf, regional variety of the Nakanai language]
-
A.
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.
-
B.
Naiki language variety
Naiki language variety refers to any of several closely related Dravidian speech forms, often mutually intelligible and regionally distinct, spoken by Naiki communities in central and southern India.
-
C.
Kunama language variety
A Kunama language variety is a specific regional or social form of the Kunama language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Kunama linguistic continuum.
-
D.
Subanen language variety
A Subanen language variety is a specific regional or social form of the Subanen language spoken by Subanen communities in the Zamboanga Peninsula and surrounding areas of the southern Philippines, characterized by distinct phonological, lexical, and grammatical features.
-
E.
Kam language variety
A Kam language variety is a specific form or dialect of the Kam language, distinguished by its unique phonological, lexical, and grammatical features within the broader Kam linguistic continuum.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.