Triple
T24279381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruvalangadu plates |
E605497
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chola inscription |
C48631
|
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: Chola inscription Context triple: [Tiruvalangadu plates, instanceOf, Chola inscription]
-
A.
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.
-
B.
Srivijaya inscription
A Srivijaya inscription is an ancient written record, typically in Old Malay or Sanskrit, produced by the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
C.
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.
-
D.
Ashokan edicts
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.
-
E.
Old Javanese inscription
An Old Javanese inscription is a historical text carved or written in the Old Javanese language, typically on stone, metal, or other durable materials, documenting political, religious, legal, or social matters in ancient Java.
- F. None of above. chosen
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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:07 a.m.