Triple
T25422335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahl dialect |
E637016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variant of Dhivehi language |
C21941
|
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: variant of Dhivehi language Context triple: [Mahl dialect, instanceOf, variant of Dhivehi language]
-
A.
Maldivian language
chosen
The Maldivian language, also known as Dhivehi, is an Indo-Aryan language spoken primarily in the Maldives, characterized by its unique Thaana script and influences from Arabic, Sinhalese, and Dravidian languages.
-
B.
regional variety of the Malagasy language
A regional variety of the Malagasy language is a geographically localized form of Malagasy characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area of Madagascar or nearby islands.
-
C.
Sabaic language variety
A Sabaic language variety is a specific form or dialect of the ancient South Arabian Sabaic language, distinguished by its unique linguistic features, geographic distribution, and historical context within the Sabaean cultural sphere.
-
D.
Nicobarese language variety
A Nicobarese language variety is a specific linguistic form or dialect within the Nicobarese branch of the Austroasiatic language family, spoken by the indigenous Nicobarese people of India’s Nicobar Islands.
-
E.
regional variety of the Sasak language
A regional variety of the Sasak language is a geographically and socially distinct form of Sasak characterized by systematic differences in pronunciation, vocabulary, and grammar from other Sasak varieties.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:57 p.m.