Triple
T5459752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashokan inscriptions |
E122567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient inscriptions |
C18119
|
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: ancient inscriptions Context triple: [Ashokan inscriptions, instanceOf, ancient inscriptions]
-
A.
ancient Greek inscription
An ancient Greek inscription is a text carved, painted, or otherwise permanently marked on durable materials such as stone, metal, or pottery in the Greek language, typically serving public, religious, legal, or commemorative purposes in antiquity.
-
B.
ancient Javanese inscription
An ancient Javanese inscription is a historical text carved or written in Old Javanese script on durable materials such as stone, metal, or clay, documenting religious, political, legal, or cultural aspects of early Javanese civilization.
-
C.
multilingual inscription
A multilingual inscription is a written text or engraving that presents the same or related content in two or more languages, often to communicate across linguistic groups or preserve information for diverse audiences.
-
D.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
-
E.
inscription corpus
An inscription corpus is a systematically collected and organized body of inscribed texts (such as carvings on stone, metal, or other durable materials) used for linguistic, historical, and archaeological analysis.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:08 p.m.