Triple
T111632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuman language family |
E2260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous language family |
C661
|
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: indigenous language family Context triple: [Yuman language family, instanceOf, indigenous language family]
-
A.
language family
chosen
A language family is a group of languages that have evolved from a common ancestral language and share systematic similarities in vocabulary, grammar, and sound patterns.
-
B.
Austronesian language
An Austronesian language is any member of a large family of languages spoken from Madagascar across Island Southeast Asia and the Pacific to Easter Island, characterized by shared phonological, grammatical, and lexical features tracing back to a common ancestral tongue.
-
C.
Malayo-Polynesian language
A Malayo-Polynesian language is a member of a large branch of the Austronesian language family spoken across Southeast Asia, Madagascar, and the Pacific islands, characterized by shared phonological, grammatical, and lexical features.
-
D.
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.
-
E.
Semitic language
A Semitic language is a member of a family of related languages originating in the Middle East and North Africa, characterized by root-based morphology and including languages such as Arabic, Hebrew, and Amharic.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.