Triple
T12103990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Setekh |
E288255
|
entity |
| Predicate | hasTransliteration |
P2508
|
FINISHED |
| Object | Setekh |
E288255
|
NE FINISHED |
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: Setekh | Statement: [Setekh, hasTransliteration, Setekh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Setekh Context triple: [Setekh, hasTransliteration, Setekh]
-
A.
Setekh
chosen
Setekh is an alternative transliteration of Set, the ancient Egyptian god associated with chaos, storms, deserts, and disorder.
-
B.
Sekhemib
Sekhemib was the Horus name of Psamtik II, a pharaoh of Egypt’s 26th Dynasty known for his military campaigns and monumental building projects.
-
C.
Sekhemti
Sekhemti is the ancient Egyptian Double Crown symbolizing the unified rule over Upper and Lower Egypt.
-
D.
Sekhemre
Sekhemre was an ancient Egyptian royal figure, likely a prince or king associated with the lineage of Pharaoh Menkaura of the Fourth Dynasty.
-
E.
Kha-sekhemui
Kha-sekhemui, better known as Khasekhemwy, was a pharaoh of Egypt’s Second Dynasty noted for reuniting Upper and Lower Egypt and for his distinctive monuments at Hierakonpolis and Abydos.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915568b9881909fc9edacefb86409 |
completed | April 10, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f677039481908f14fa12b9b86910 |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.