Triple
T13363556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem Chronicle |
E318879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Babylonian chronicle |
C12104
|
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: Babylonian chronicle Context triple: [Jerusalem Chronicle, instanceOf, Babylonian chronicle]
-
A.
Mesopotamian creation epic
A Mesopotamian creation epic is a mythological narrative poem that explains the origins of the cosmos, gods, and human society in ancient Mesopotamia, often emphasizing divine conflict and the establishment of cosmic order.
-
B.
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.
-
C.
Sumerian temple hymn
A Sumerian temple hymn is an ancient Mesopotamian poetic composition that praises a specific temple and its deity, celebrating the sacred space’s divine presence, power, and ritual significance.
-
D.
cuneiform tablet series
chosen
A cuneiform tablet series is a sequentially organized set of inscribed clay tablets that together comprise a larger literary, administrative, legal, or scholarly work in ancient Mesopotamian writing traditions.
-
E.
Byzantine chronicle
A Byzantine chronicle is a historical narrative, often arranged annalistically, that records events of the Byzantine Empire and surrounding regions, typically blending factual reporting with religious interpretation and classical traditions.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:32 p.m.