Triple
T1259274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abkhazians |
E12461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northwest Caucasian people |
C7198
|
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: Northwest Caucasian people Context triple: [Abkhazians, instanceOf, Northwest Caucasian people]
-
A.
Samoyedic people
Samoyedic people are a group of indigenous peoples of northern Eurasia, primarily in northern Russia, who speak Samoyedic languages of the Uralic family and traditionally practice reindeer herding, fishing, and hunting in Arctic and subarctic environments.
-
B.
Finno-Ugric people
Finno-Ugric people are a group of ethnolinguistic populations in Northern and Eastern Europe and Western Siberia who speak Finno-Ugric languages, including Finns, Estonians, and various Uralic-speaking minorities such as the Sami, Mari, and Udmurts.
-
C.
Northwest Caucasian language
A Northwest Caucasian language is a member of a small family of indigenous languages spoken in the northwestern Caucasus region, characterized by complex consonant systems, minimal vowel inventories, and rich verbal morphology.
-
D.
South Slavic people
South Slavic people are an ethnolinguistic group in Southeast Europe who speak South Slavic languages and share related historical, cultural, and regional ties.
-
E.
Uralic language
A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:50 p.m.