Triple
T13126509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotak family |
E311856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pashtun lineage |
C29118
|
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: Pashtun lineage Context triple: [Hotak family, instanceOf, Pashtun lineage]
-
A.
Pashtun tribe
chosen
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.
-
B.
Arab tribal lineage
Arab tribal lineage is a kinship-based social structure that traces descent—often patrilineally—from a common ancestor, organizing individuals and groups into nested tribes, clans, and families that shape identity, status, and social obligations.
-
C.
Karbi clan
A Karbi clan is a traditional exogamous kinship group within the Karbi community that organizes social identity, marriage rules, and ritual responsibilities.
-
D.
Pakistani political dynasty
A Pakistani political dynasty is a powerful family whose members, across multiple generations, occupy influential political positions and shape national or regional governance, often leveraging inherited status, patronage networks, and party control.
-
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.
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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:07 p.m.