Triple
T23279186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapsugs |
E588810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Circassian subgroup |
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: Circassian subgroup Context triple: [Shapsugs, instanceOf, Circassian subgroup]
-
A.
Abkhaz subgroup
The Abkhaz subgroup is a conceptual class representing a distinct subset of the Abkhaz people characterized by shared linguistic, cultural, or regional traits within the broader Abkhaz ethnic community.
-
B.
Aimaq subgroup
Aimaq subgroup refers to a distinct tribal or regional division within the Aimaq people of Afghanistan and neighboring areas, characterized by shared lineage, dialect, and cultural practices.
-
C.
Georgian subgroup
The Georgian subgroup is a classification of related dialects or varieties within the Georgian language that share common linguistic features and regional or social characteristics.
-
D.
Northwest Caucasian people
chosen
Northwest Caucasian people are an indigenous group of ethnic communities native to the northwestern Caucasus region, characterized by distinct languages, cultures, and historical traditions.
-
E.
Northeast Caucasian people
Northeast Caucasian people are an ethnolinguistic group indigenous to the northeastern Caucasus region, encompassing diverse communities such as Chechens, Avars, and Lezgins who share related Northeast Caucasian languages and cultural traditions.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 4:49 p.m.