Triple
T10438594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maidu language |
E246106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maiduan language |
C27730
|
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: Maiduan language Context triple: [Maidu language, instanceOf, Maiduan language]
-
A.
Mon language
Mon language is an Austroasiatic language historically spoken by the Mon people of Myanmar and Thailand, notable for its ancient inscriptions and significant influence on the region’s scripts and cultures.
-
B.
Munda language
The Munda language is a member of the Austroasiatic language family spoken primarily by indigenous Munda communities in eastern and central India, characterized by agglutinative morphology and distinct phonological features.
-
C.
Cham language
Cham language is an Austronesian language spoken by the Cham people of Vietnam and Cambodia, notable for its historical use of an Indic-derived script and its role in the former Champa kingdom.
-
D.
Astur-Leonese language
The Astur-Leonese language is a Romance language continuum spoken primarily in Asturias, León, and surrounding regions of northwestern Spain, characterized by its own distinct phonological, lexical, and grammatical features separate from Spanish and Galician-Portuguese.
-
E.
Batanic language
The Batanic language is a subgroup of Austronesian languages spoken primarily in the Batanes Islands of the northern Philippines and nearby areas, characterized by shared phonological and lexical features distinct from neighboring Philippine languages.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:14 p.m.