Triple
T34111925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sindhi Nanakpanthis |
E874859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sindhi Hindu subgroup |
C49433
|
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: Sindhi Hindu subgroup Context triple: [Sindhi Nanakpanthis, instanceOf, Sindhi Hindu subgroup]
-
A.
Sindhi tribe
chosen
The Sindhi tribe is an ethnolinguistic community originating from the Sindh region, characterized by a shared Sindhi language, rich cultural traditions, and a historical legacy shaped by trade, Sufism, and regional migrations.
-
B.
Tharu subgroup
A Tharu subgroup is a distinct cultural, linguistic, or regional division within the broader Tharu ethnic community, characterized by its own traditions, dialects, and social practices.
-
C.
Yadava subgroup
The Yadava subgroup is a conceptual class representing a distinct lineage or faction within the broader Yadava community, typically characterized by shared ancestry, cultural practices, and social identity.
-
D.
Adi subgroup
An Adi subgroup is a smaller, distinct social or clan division within the Adi community of Arunachal Pradesh, typically defined by shared ancestry, territory, and cultural practices.
-
E.
subgroup of the Adi people
A subgroup of the Adi people is a distinct clan or community within the larger Adi ethnic group, sharing core Adi cultural traits while maintaining its own specific traditions, dialectal features, 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:53 a.m.