Triple
T28691608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kültepe tablet corpus |
E729299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Old Assyrian text corpus |
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: Old Assyrian text corpus Context triple: [Kültepe tablet corpus, instanceOf, Old Assyrian text corpus]
-
A.
ancient Mesopotamian text
An ancient Mesopotamian text is a written document from early civilizations in the Tigris-Euphrates region, typically inscribed on clay tablets in cuneiform script, recording everything from myths and laws to economic transactions and scholarly knowledge.
-
B.
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.
-
C.
Old Babylonian period text
An Old Babylonian period text is a written document produced in Mesopotamia roughly between 2000–1600 BCE, typically inscribed in cuneiform on clay tablets and reflecting the administrative, legal, literary, or scholarly practices of that era.
-
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.
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.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:36 a.m.