Triple
T23151273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashokan rock edicts at Dhauli |
E578328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rock edicts |
C44587
|
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: rock edicts Context triple: [Ashokan rock edicts at Dhauli, instanceOf, rock edicts]
-
A.
Ashokan edicts
chosen
Ashokan edicts are a series of inscriptions on pillars, rocks, and cave walls issued by the Mauryan emperor Ashoka in the 3rd century BCE, proclaiming his policies, moral teachings, and commitment to dharma across his empire.
-
B.
Kharoṣṭhī inscription
A Kharoṣṭhī inscription is a written text carved or inscribed using the ancient Kharoṣṭhī script, primarily found on stone, metal, pottery, or other durable materials in the northwestern regions of the Indian subcontinent and Central Asia.
-
C.
ancient inscriptions
Ancient inscriptions are texts or symbols carved, engraved, or written on durable materials such as stone, metal, or clay by past civilizations, serving as primary evidence of their language, culture, beliefs, and historical events.
-
D.
Srivijayan inscription
A Srivijayan inscription is an ancient written record, typically carved in stone or metal, produced under the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
E.
religious inscription
A religious inscription is a text carved, written, or otherwise permanently recorded on a durable surface that conveys sacred messages, prayers, dedications, or doctrinal statements associated with a particular faith tradition.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:01 p.m.