Triple
T4910908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parashara Smriti |
E110228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dharmashastra text |
C1770
|
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: Dharmashastra text Context triple: [Parashara Smriti, instanceOf, Dharmashastra text]
-
A.
Sanskrit literature
chosen
Sanskrit literature is the body of classical and post-classical writings in the Sanskrit language, encompassing religious scriptures, epic poetry, drama, philosophy, science, and aesthetics that shaped much of South Asian intellectual and cultural history.
-
B.
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.
-
C.
religious text carrier
A religious text carrier is an entity (person, object, or medium) that transports, preserves, or conveys sacred writings from one place, time, or audience to another.
-
D.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
E.
Roman law textbook
A Roman law textbook is a comprehensive instructional volume that explains the principles, institutions, procedures, and historical development of Roman legal systems, often with translations, commentary, and case analyses.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.