Triple
T25505988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kadesh Treaty tablet |
E639245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern artifact |
C18825
|
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 Near Eastern artifact Context triple: [Kadesh Treaty tablet, instanceOf, ancient Near Eastern artifact]
-
A.
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.
-
B.
ancient Egyptian artifact
An ancient Egyptian artifact is a physical object created or used in ancient Egypt that reflects the civilization’s religious beliefs, daily life, artistic styles, or technological achievements.
-
C.
ancient Near Eastern art
chosen
Ancient Near Eastern art encompasses the visual and material creations of early civilizations in Mesopotamia, Anatolia, the Levant, and Persia, reflecting their religious beliefs, political power, and daily life through sculpture, reliefs, architecture, and decorative objects.
-
D.
archaeological artifact
An archaeological artifact is any portable object made, modified, or used by humans in the past that is recovered through archaeological investigation and studied to understand past cultures and activities.
-
E.
biblical artifact
A biblical artifact is a physical object, such as a manuscript, inscription, tool, or relic, that is historically or culturally connected to the people, places, or events described in the Bible.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:47 p.m.