Triple
T12104238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decree of Canopus |
E288262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trilingual inscription |
C15764
|
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: trilingual inscription Context triple: [Decree of Canopus, instanceOf, trilingual inscription]
-
A.
multilingual inscription
chosen
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.
-
B.
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.
-
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.
mosaic inscription
A mosaic inscription is a text or message formed by arranging small, colored pieces of stone, glass, or tile within a mosaic design, typically serving decorative, commemorative, or religious purposes.
-
E.
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.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:48 p.m.