Triple
T13367885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Ocean contact varieties of Hindi |
E318987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindi-based contact language continuum |
C1720
|
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: Hindi-based contact language continuum Context triple: [Indian Ocean contact varieties of Hindi, instanceOf, Hindi-based contact language continuum]
-
A.
dialect continuum
chosen
A dialect continuum is a range of geographically adjacent language varieties that change gradually from one area to the next, so that neighboring dialects are mutually intelligible but those at distant ends may not be.
-
B.
Niger-Congo language reference system
A Niger-Congo language reference system is a structured framework for cataloging, describing, and cross-referencing the languages of the Niger-Congo family, including their classifications, features, and relationships.
-
C.
Bihari languages
Bihari languages are a group of closely related Indo-Aryan languages and dialects spoken primarily in the Indian state of Bihar and surrounding regions, including Bhojpuri, Maithili, and Magahi.
-
D.
tonal language
A tonal language is a language in which differences in pitch or intonation patterns on syllables or words serve to distinguish meaning between otherwise identical sequences of sounds.
-
E.
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.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:32 p.m.