Triple
T10686106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osage orthography |
E251880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Osage-language writing system |
C28625
|
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: Osage-language writing system Context triple: [Osage orthography, instanceOf, Osage-language writing system]
-
A.
Mesoamerican writing system
A Mesoamerican writing system is a structured set of visual symbols and conventions developed by pre-Columbian cultures in Mesoamerica to record language, convey information, and represent cultural, religious, and political concepts.
-
B.
Mesoamerican script
A Mesoamerican script is a writing system developed by pre-Columbian cultures in Mesoamerica, using combinations of logographic and syllabic signs to record language, history, and ritual knowledge.
-
C.
Numic language
A Numic language is any member of a branch of the Uto-Aztecan language family spoken traditionally by Indigenous peoples of the Great Basin and surrounding regions of the western United States, including languages such as Northern Paiute, Shoshoni, and Comanche.
-
D.
Hokan language
Hokan language is a proposed but controversial grouping of several Native American language families and isolates of western North America, hypothesized to share a distant common ancestor.
-
E.
Hmong romanization system
A Hmong romanization system is a standardized method of writing the Hmong language using the Latin alphabet, encoding its tones, consonants, and vowels for consistent reading and writing.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:10 p.m.