Triple
T34473980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo Stone |
E884980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | royal annals inscription |
C28308
|
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 annals inscription Context triple: [Cairo Stone, instanceOf, royal annals inscription]
-
A.
royal annals
chosen
Royal annals are chronological records maintained by or for a monarchy that document significant political, military, religious, and ceremonial events of a ruler’s reign.
-
B.
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.
-
C.
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.
-
D.
Sasanian royal inscription
A Sasanian royal inscription is an official monumental text commissioned by Sasanian kings, typically carved on rock faces, buildings, or artifacts, proclaiming their titles, achievements, religious affiliations, and political authority.
-
E.
Assyrian royal inscription
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.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.