Triple
T2102123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic of Gilgamesh |
E37113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Mesopotamian literature |
C1813
|
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: ancient Mesopotamian literature Context triple: [Epic of Gilgamesh, instanceOf, ancient Mesopotamian literature]
-
A.
ancient Greek literature
Ancient Greek literature encompasses the epic, lyric, dramatic, historical, and philosophical writings produced in the Greek language from the archaic through the Hellenistic periods, foundational to Western literary and intellectual traditions.
-
B.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
C.
Sanskrit literature
Sanskrit literature is the body of classical and post-classical writings in the Sanskrit language, encompassing religious scriptures, epic poetry, drama, philosophy, science, and aesthetics that shaped much of South Asian intellectual and cultural history.
-
D.
mythological text
chosen
A mythological text is a written work that records, interprets, or retells traditional myths, deities, and cosmological narratives of a culture, often explaining origins, values, and supernatural events.
-
E.
ancient language
An ancient language is a historically significant, no-longer-natively-spoken linguistic system preserved through inscriptions, manuscripts, and scholarly reconstruction.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:43 p.m.