Triple
T11086673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karnak Temple inscriptions |
E262137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Egyptian inscription 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 Egyptian inscription corpus Context triple: [Karnak Temple inscriptions, instanceOf, ancient Egyptian inscription corpus]
-
A.
Egyptology collection
An Egyptology collection is an organized assemblage of artifacts, texts, and related materials that document and support the study of ancient Egyptian history, culture, language, and religion.
-
B.
ancient inscriptions
Ancient inscriptions are texts or symbols carved, engraved, or written on durable materials such as stone, metal, or clay by past civilizations, serving as primary evidence of their language, culture, beliefs, and historical events.
-
C.
Proto-Canaanite inscription
A Proto-Canaanite inscription is an early alphabetic text, typically carved on stone or pottery in the Levant during the late second millennium BCE, representing one of the earliest known stages of the Canaanite (and thus later Phoenician and Hebrew) writing system.
-
D.
ancient Egyptian script
Ancient Egyptian script is a writing system that used hieroglyphic, hieratic, and demotic forms to record the language, religion, administration, and culture of ancient Egypt over several millennia.
-
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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.