Triple
T3670047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amarna letters |
E77856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern text corpus |
C9642
|
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 text corpus Context triple: [Amarna letters, instanceOf, ancient Near Eastern text corpus]
-
A.
ancient literature
Ancient literature encompasses the written works, myths, epics, religious texts, and philosophical writings produced by early civilizations that reveal their cultures, beliefs, and historical experiences.
-
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.
bibliographical corpus
A bibliographical corpus is a structured collection of bibliographic records or references, typically compiled for systematic analysis, cataloging, or research on published works.
-
D.
ancient manuscripts
Ancient manuscripts are original handwritten documents from past civilizations, typically preserved on materials like papyrus, parchment, or early paper, that provide primary evidence of historical, religious, literary, or scientific thought.
-
E.
inscription corpus
chosen
An inscription corpus is a systematically collected and organized body of inscribed texts (such as carvings on stone, metal, or other durable materials) used for linguistic, historical, and archaeological analysis.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.