Triple
T24279425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leiden copperplate inscription |
E605498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | copperplate inscription |
C48632
|
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: copperplate inscription Context triple: [Leiden copperplate inscription, instanceOf, copperplate inscription]
-
A.
royal building inscription
A royal building inscription is a formal text, typically carved on or attached to a structure, that records a ruler’s role in commissioning, constructing, restoring, or dedicating that building, often highlighting their authority, piety, and achievements.
-
B.
architectural inscription
An architectural inscription is a text or symbolic marking integrated into a building or structure that conveys information, commemoration, or meaning related to its purpose, creators, or historical context.
-
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.
Hebrew inscription
A Hebrew inscription is a text carved, written, or engraved in the Hebrew language and script on a durable surface such as stone, metal, pottery, or parchment, often serving religious, commemorative, legal, or decorative purposes.
-
E.
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.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:07 a.m.