Triple
T3718990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of Tiglath-Pileser III |
E81595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal inscription |
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 Context triple: [Annals of Tiglath-Pileser III, instanceOf, royal inscription]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
royal authorization
Royal authorization is the formal approval or sanction granted by a monarch that legitimizes specific actions, decisions, or privileges within a realm.
-
E.
Etruscan inscription
An Etruscan inscription is a text written in the ancient Etruscan language, typically carved or painted on durable materials such as stone, metal, or pottery, providing evidence of the culture, religion, and daily life of the Etruscan civilization.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.