Triple
T19767722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siloam Inscription |
E474801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal commemorative inscription |
C27698
|
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 commemorative inscription Context triple: [Siloam Inscription, instanceOf, royal commemorative inscription]
-
A.
commemorative inscription
chosen
A commemorative inscription is a formally written text, often engraved or carved on a durable surface, that records and honors a person, event, or achievement for posterity.
-
B.
royal encomium
A royal encomium is a formal, often elaborate work of praise that glorifies a monarch’s virtues, achievements, and divine or historical legitimacy.
-
C.
war memorial inscription
A war memorial inscription is a formally composed text engraved or displayed on a monument to commemorate individuals or groups who served or died in military conflict, often expressing remembrance, honor, and collective grief.
-
D.
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.
-
E.
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.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:48 p.m.