Triple
T23071498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taymuri |
E575207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub-group of Aimaq people |
C20024
|
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: sub-group of Aimaq people Context triple: [Taymuri, instanceOf, sub-group of Aimaq people]
-
A.
Aimaq subgroup
chosen
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.
-
B.
Nuristani people
The Nuristani people are an indigenous ethnic group primarily inhabiting the remote Nuristan province of eastern Afghanistan, known for their distinct Indo-Iranian language cluster, unique cultural traditions, and historical transition from pre-Islamic beliefs to Islam in the late 19th century.
-
C.
Ga people subgroup
A Ga people subgroup is a distinct cultural, social, or lineage-based division within the broader Ga ethnic group, characterized by shared ancestry, traditions, dialectal features, and localized community identity.
-
D.
Nakh people
The Nakh people are a group of closely related Northeast Caucasian ethnic communities, primarily including the Chechens and Ingush, characterized by a shared Nakh language branch, highland cultural traditions, and historical presence in the North Caucasus region.
-
E.
subgroup of Gond people
A subgroup of Gond people is a distinct clan or community within the larger Gond ethnic group, sharing common ancestry, cultural practices, and social identity.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:56 p.m.