Triple
T19594312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smriti |
E470312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of Hindu religious law |
C18134
|
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: source of Hindu religious law Context triple: [Smriti, instanceOf, source of Hindu religious law]
-
A.
Hindu religious texts
Hindu religious texts are a diverse body of ancient and medieval scriptures—including the Vedas, Upanishads, epics like the Mahabharata and Ramayana, and numerous Puranas and devotional works—that articulate Hindu philosophy, mythology, rituals, and ethical teachings.
-
B.
source of dharma
chosen
A source of dharma is any person, text, tradition, or experiential insight that authoritatively reveals, preserves, or clarifies the principles of righteous conduct and ultimate truth.
-
C.
source of Byzantine law
A source of Byzantine law is any authoritative origin—such as imperial legislation, ecclesiastical canons, juristic writings, or customary practices—from which the legal norms of the Byzantine Empire were derived and recognized.
-
D.
Hindu reformist text
A Hindu reformist text is a written work that critiques existing religious practices and beliefs within Hinduism and advocates changes to align them with contemporary ethical, social, or rational ideals.
-
E.
Mughal-era legal code
A Mughal-era legal code is a structured body of laws, regulations, and judicial principles developed under the Mughal Empire that governed civil, criminal, fiscal, and religious matters by blending Islamic jurisprudence with local customs and imperial decrees.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.