Triple
T12888432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shebitku |
E308292
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Piye |
E276350
|
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: Piye | Statement: [Shebitku, father, Piye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piye Context triple: [Shebitku, father, Piye]
-
A.
Piye
chosen
Piye was an ancient Kushite king who conquered and unified Egypt in the 8th century BCE, founding the Twenty-fifth Dynasty.
-
B.
Taharqa
Taharqa was a prominent pharaoh of Egypt’s 25th (Kushite) Dynasty, known for his extensive building projects and resistance against Assyrian expansion in the 7th century BCE.
-
C.
Tachenwit
Tachenwit is an alternative name for the Chenoua language, a Berber language spoken in northern Algeria.
-
D.
Sawiris
Sawiris is a prominent Egyptian business family best known for its influential role in construction, telecommunications, and investment through the Orascom group of companies.
-
E.
Mutemhat
Mutemhat was an ancient Egyptian queen consort of the 22nd Dynasty pharaoh Osorkon II.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714581988190afc720ffd7797860 |
completed | April 10, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8ccee708190bb4caa604386e3a3 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 5:39 p.m.