Triple
T17937568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andhaka |
E448507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dynasty in Hindu tradition |
C17101
|
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: dynasty in Hindu tradition Context triple: [Andhaka, instanceOf, dynasty in Hindu tradition]
-
A.
Hindu royal lineage
chosen
A Hindu royal lineage is a hereditary line of rulers and nobles within Hindu society, traditionally legitimized by sacred texts, divine ancestry, and ritual authority.
-
B.
dynasty
A dynasty is a succession of rulers or leaders from the same family or lineage, often maintaining power over multiple generations within a state or organization.
-
C.
ruling dynasty of North India
A ruling dynasty of North India is a hereditary line of monarchs or sovereign families that exercised political authority, controlled territory, and shaped the region’s cultural, social, and economic life over successive generations.
-
D.
denomination of Hinduism
A denomination of Hinduism is a distinct religious tradition within Hinduism characterized by its own set of core deities, philosophies, rituals, and community practices while still sharing the broader Hindu cultural and scriptural framework.
-
E.
Hindu kingdom
A Hindu kingdom is a pre-modern or early modern polity in South Asia whose ruling dynasty, state ideology, and major institutions were grounded in Hindu religious, social, and cultural traditions.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.