Triple
T22424052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aapep |
E554321
|
entity |
| Predicate | transliteratedAs |
P5923
|
FINISHED |
| Object | ꜥꜣpp |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ꜥꜣpp | Statement: [Aapep, transliteratedAs, ꜥꜣpp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ꜥꜣpp Context triple: [Aapep, transliteratedAs, ꜥꜣpp]
-
A.
tꜣ-šmꜥ
tꜣ-šmꜥ is the ancient Egyptian name for Ta-Shema, the southern part of Upper Egypt in pharaonic geography.
-
B.
Aapep
chosen
Aapep is an alternate name for Apep, the ancient Egyptian serpent deity embodying chaos and the eternal enemy of the sun god Ra.
-
C.
Wepwawetemsaf
Wepwawetemsaf was a little-known and possibly short-reigning pharaoh who ruled during the politically fragmented Second Intermediate Period of ancient Egypt.
-
D.
Sopdu
Sopdu is an ancient Egyptian god associated with the eastern frontier, often linked to protection, war, and the rising sun.
-
E.
Nfr-ḥtp.s
Nfr-ḥtp.s is the hieroglyphic name of Neferhetepes II, an ancient Egyptian royal woman of the 5th Dynasty.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2af620819083338127e78137dc |
completed | April 29, 2026, 1:08 a.m. |
Created at: April 16, 2026, 8:47 p.m.