Triple

T23543037
Position Surface form Disambiguated ID Type / Status
Subject Taimuri Aimaq E577807 entity
Predicate instanceOf P0 FINISHED
Object Aimaq tribe C47798 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: Aimaq tribe
Context triple: [Taimuri Aimaq, instanceOf, Aimaq tribe]
  • A. Oghuz Turkic tribe
    An Oghuz Turkic tribe is a socio-political and kinship-based group descended from the historical Oghuz Turks, sharing common lineage, language, and cultural traditions within the broader Oghuz Turkic world.
  • B. Pashtun tribe
    A Pashtun tribe is a kinship-based social unit within the Pashtun ethnic group, defined by shared ancestry, cultural traditions, and customary laws (Pashtunwali) that structure social, political, and territorial organization.
  • C. 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.
  • D. Naga tribe
    A Naga tribe is an indigenous ethnic community from the northeastern region of India and northwestern Myanmar, characterized by distinct languages, rich oral traditions, and unique cultural practices including elaborate festivals and traditional attire.
  • E. 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.
  • 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_69e245f9d5d08190a4a20004e1784e20 completed April 17, 2026, 2:38 p.m.
Created at: April 17, 2026, 6:10 p.m.