Triple
T6220482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persepolis inscriptions |
E139099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal inscription corpus |
C9642
|
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: royal inscription corpus Context triple: [Persepolis inscriptions, instanceOf, royal inscription corpus]
-
A.
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.
-
B.
inscription corpus
chosen
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.
-
C.
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.
-
D.
Oscan inscription
An Oscan inscription is a written text in the Oscan language, typically carved on stone, metal, or pottery by ancient Italic peoples, providing evidence of their language, culture, and public or religious life.
-
E.
cuneiform tablets collection
A cuneiform tablets collection is an organized assemblage of inscribed clay tablets that preserves and categorizes ancient written records for study, interpretation, and cultural heritage.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:21 p.m.