Triple
T9758475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tale of Sinuhe |
E236610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian literary work |
C19507
|
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 Egyptian literary work Context triple: [The Tale of Sinuhe, instanceOf, ancient Egyptian literary work]
-
A.
ancient literary work
An ancient literary work is a written composition created in antiquity that reflects the language, culture, beliefs, and artistic expression of early civilizations.
-
B.
Sumerian mythological poem
A Sumerian mythological poem is an ancient Mesopotamian narrative verse that recounts the deeds of gods, heroes, and cosmic events, often explaining the origins of the world, social institutions, and divine-human relationships.
-
C.
Middle Egyptian narrative
chosen
A Middle Egyptian narrative is a literary text written in the classical phase of the Egyptian language that recounts events—often blending history, myth, and moral instruction—through prose or poetic storytelling.
-
D.
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.
-
E.
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.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:24 p.m.