Triple
T10337672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abydos King List |
E243049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical inscription |
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: historical inscription Context triple: [Abydos King List, instanceOf, historical inscription]
-
A.
ancient inscriptions
chosen
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.
religious inscription
A religious inscription is a text carved, written, or otherwise permanently recorded on a durable surface that conveys sacred messages, prayers, dedications, or doctrinal statements associated with a particular faith tradition.
-
C.
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.
-
D.
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.
-
E.
Georgian inscription
A Georgian inscription is a text carved, written, or otherwise rendered in the Georgian script, typically found on monuments, buildings, artifacts, or manuscripts, conveying historical, religious, or commemorative information.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:54 a.m.