Triple
T30169592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weld-Blundell Prism |
E766882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sumerian King List manuscript |
C47265
|
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: Sumerian King List manuscript Context triple: [Weld-Blundell Prism, instanceOf, Sumerian King List manuscript]
-
A.
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.
-
B.
Proto-Canaanite inscription
A Proto-Canaanite inscription is an early alphabetic text, typically carved on stone or pottery in the Levant during the late second millennium BCE, representing one of the earliest known stages of the Canaanite (and thus later Phoenician and Hebrew) writing system.
-
C.
cuneiform document
chosen
A cuneiform document is a written artifact, typically on clay or stone, bearing information recorded in the wedge-shaped cuneiform script used by ancient Near Eastern civilizations.
-
D.
Aramaic papyri
Aramaic papyri are ancient documents written in the Aramaic language on papyrus, typically comprising letters, legal contracts, and administrative records that illuminate the social, economic, and political life of Near Eastern communities.
-
E.
Ugaritic text
An Ugaritic text is an ancient written document from the city of Ugarit, inscribed in the Ugaritic cuneiform script and typically recording literary, religious, administrative, or legal content in the Ugaritic language.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:24 p.m.