Triple
T15837660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of Shalmaneser III |
E384024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian historical source |
C6136
|
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 historical source Context triple: [Annals of Shalmaneser III, instanceOf, Assyrian historical source]
-
A.
Sumerian literary text
A Sumerian literary text is a written composition in the Sumerian language, typically preserved on clay tablets, that conveys narratives, hymns, myths, wisdom, or other imaginative and artistic content rather than purely administrative or practical information.
-
B.
Sumerian artifact
A Sumerian artifact is a physical object created or used by the ancient Sumerian civilization that reflects their daily life, beliefs, technology, or artistic expression.
-
C.
Sumerian wisdom text
A Sumerian wisdom text is an ancient Mesopotamian didactic composition, often in poetic form, that imparts moral instruction, practical advice, and reflections on proper conduct and social order.
-
D.
historical source
chosen
A historical source is any original material—such as documents, artifacts, recordings, or testimonies—created in the past that provides evidence or information about historical events, people, or conditions.
-
E.
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.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.