Triple
T22506894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inscription of Nebuchadnezzar II |
E556412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal building inscription |
C46419
|
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 building inscription Context triple: [inscription of Nebuchadnezzar II, instanceOf, royal building inscription]
-
A.
Kharoṣṭhī inscription
A Kharoṣṭhī inscription is a written text carved or inscribed using the ancient Kharoṣṭhī script, primarily found on stone, metal, pottery, or other durable materials in the northwestern regions of the Indian subcontinent and Central Asia.
-
B.
royal government building
A royal government building is an official structure where a monarchy’s administrative, ceremonial, and governing functions are conducted and represented.
-
C.
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.
-
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.
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.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.