Triple
T32658144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurk Monolith |
E834920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian stone monument |
C47266
|
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: Assyrian stone monument Context triple: [Kurk Monolith, instanceOf, Assyrian stone monument]
-
A.
Akkadian monument
An Akkadian monument is a commemorative or dedicatory structure, such as a stele, statue, or inscribed stone, created by the Akkadian civilization to record political achievements, religious devotion, or historical events.
-
B.
Elamite monument
An Elamite monument is a commemorative or religious structure created by the ancient Elamite civilization, typically inscribed or carved to record royal achievements, religious dedications, or historical events.
-
C.
Assyrian royal inscription
chosen
An Assyrian royal inscription is a formal cuneiform text commissioned by an Assyrian king to record and glorify his military campaigns, building projects, piety, and divine legitimacy.
-
D.
Sasanian rock relief
A Sasanian rock relief is a large-scale stone carving, typically on cliff faces or rock walls, created during the Sasanian Empire to depict royal ceremonies, victories, and religious scenes as expressions of imperial power and ideology.
-
E.
Assyrian palace reliefs
Assyrian palace reliefs are intricately carved stone panels that decorated royal Assyrian palaces, depicting military campaigns, hunting scenes, religious rituals, and courtly life to glorify the king’s power and divine authority.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:08 a.m.