Triple
T13923722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandeali |
E334808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Indo-Aryan language |
C6327
|
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 Indo-Aryan language Context triple: [Mandeali, instanceOf, Northern Indo-Aryan language]
-
A.
Indo-Aryan language variety
chosen
An Indo-Aryan language variety is a specific form or dialect of a language within the Indo-Aryan branch of the Indo-European family, characterized by shared historical origins and linguistic features such as phonology, grammar, and vocabulary.
-
B.
Dravidian language
A Dravidian language is a member of a family of primarily South Indian and Sri Lankan languages, such as Tamil, Telugu, Kannada, and Malayalam, that share common historical origins and structural features distinct from Indo-European languages.
-
C.
Indo-Aryan people
Indo-Aryan people are a diverse group of ethnolinguistic communities in South Asia who speak Indo-Aryan languages, a major branch of the Indo-European language family, and share related historical and cultural roots.
-
D.
Dardic language
A Dardic language is a member of a subgroup of the Indo-Aryan languages spoken primarily in the mountainous regions of northern Pakistan, northwestern India, and eastern Afghanistan, characterized by distinct phonological and lexical features.
-
E.
Indo-European language
An Indo-European language is a member of a large family of related languages spoken across Europe and parts of Asia, all descended from a common prehistoric ancestor known as Proto-Indo-European.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.