Triple
T7253763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabaka |
E157667
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Shebitku |
E308292
|
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: Shebitku | Statement: [Shabaka, successor, Shebitku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shebitku Context triple: [Shabaka, successor, Shebitku]
-
A.
Shebitku
chosen
Shebitku was a Kushite king of the 25th Dynasty of ancient Egypt, known for consolidating Nubian rule over Egypt and engaging in conflicts with the expanding Assyrian Empire.
-
B.
Seshemetka
Seshemetka was an early ancient Egyptian queen consort of the 1st Dynasty, known primarily as a wife of King Djer.
-
C.
Sekhemti
Sekhemti is the ancient Egyptian Double Crown symbolizing the unified rule over Upper and Lower Egypt.
-
D.
Tashmetu-sharrat
Tashmetu-sharrat was a Neo-Assyrian queen and consort of King Sennacherib, known from royal inscriptions and administrative records of his reign.
-
E.
Wahibre
Wahibre was the throne name of Psamtik I, a 26th Dynasty pharaoh who reunified Egypt and initiated the Late Period’s political and cultural revival.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9f55b4819081a43e7a01eda154 |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8eee797a881909548186742cf7b66 |
completed | March 29, 2026, 9:20 a.m. |
Created at: March 27, 2026, 2:56 p.m.