Triple
T22014108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajagopalachari family |
E543658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Indian family |
C14723
|
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: South Indian family Context triple: [Rajagopalachari family, instanceOf, South Indian family]
-
A.
Indian family
chosen
An Indian family is a close-knit social unit typically spanning multiple generations, bound by strong cultural traditions, shared responsibilities, and deep interdependence among its members.
-
B.
South Asian family
A South Asian family is a multigenerational, kinship-centered social unit typically characterized by strong interdependence, respect for elders, shared cultural and religious practices, and close ties with extended relatives.
-
C.
South Indian royal dynasty
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, culture, religion, and art over successive generations.
-
D.
South Indian surname
A South Indian surname is a family or lineage name originating from the southern states of India, often reflecting ancestral village, caste, profession, or linguistic community.
-
E.
South Indian kingdom
A South Indian kingdom is a historically or culturally defined political entity located in the southern part of the Indian subcontinent, characterized by distinct Dravidian languages, traditions, and regional governance.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:22 p.m.