Triple
T22040382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhen |
E544621
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Sekhen-ka |
—
|
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: Sekhen-ka | Statement: [Sekhen, alsoKnownAs, Sekhen-ka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sekhen-ka Context triple: [Sekhen, alsoKnownAs, Sekhen-ka]
-
A.
Sekhen
chosen
Sekhen is an alternative name for the ancient Egyptian king Ka, an early ruler of the First Dynasty period.
-
B.
Harkhuf
Harkhuf was an important Old Kingdom Egyptian official and explorer known for his expeditions to Nubia during the Sixth Dynasty.
-
C.
Khendjer
Khendjer was a relatively obscure pharaoh of Egypt’s 13th Dynasty, known primarily from a few monuments and scarabs that attest to his short reign during the unstable Second Intermediate Period.
-
D.
Nekheb
Nekheb was an ancient Egyptian city in Upper Egypt, closely associated with the vulture goddess Nekhbet and serving as an important religious and political center.
-
E.
Kaa-Khem
Kaa-Khem is the local name for the Little Yenisei River, a tributary of the Yenisei flowing through the Tuva region of southern Siberia.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:25 p.m.