Triple
T12393574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliot Indian Bible |
E296058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Algonquian-language text |
C31401
|
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: Algonquian-language text Context triple: [Eliot Indian Bible, instanceOf, Algonquian-language text]
-
A.
Algonquian language
An Algonquian language is any member of a family of Indigenous languages of North America, historically spoken from the Atlantic coast to the Great Plains and characterized by complex morphology and polysynthetic structure.
-
B.
Osage-language writing system
The Osage-language writing system is a modern, standardized orthography, including a unique alphabet, designed specifically to represent the sounds and structure of the Osage language accurately and support its revitalization.
-
C.
Native American language
A Native American language is any of the indigenous languages historically and currently spoken by the Native peoples of the Americas, each embodying unique cultural knowledge, traditions, and worldviews.
-
D.
Muskogean language
A Muskogean language is any member of a family of Native American languages originally spoken in the southeastern United States, including Creek, Choctaw, Chickasaw, and related tongues.
-
E.
Caddoan language
A Caddoan language is any member of a small family of Indigenous languages of the central United States, historically spoken by Caddo, Wichita, Pawnee, and related peoples, characterized by complex verb morphology and now mostly endangered or extinct.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:54 p.m.