Triple

T11629139
Position Surface form Disambiguated ID Type / Status
Subject Kushite royal family E276349 entity
Predicate notableMember P10 FINISHED
Object Amanishakheto E750912 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: Amanishakheto | Statement: [Kushite royal family, notableMember, Amanishakheto]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amanishakheto
Context triple: [Kushite royal family, notableMember, Amanishakheto]
  • A. Amanishakheto chosen
    Amanishakheto was a powerful queen of the ancient Kingdom of Kush, known for her military leadership and richly adorned royal tomb at Meroë.
  • B. Akhet
    Akhet is the ancient Egyptian season of the Nile’s annual inundation, marking the flooding and renewal of the land.
  • C. Sekhen
    Sekhen is an alternative name for the ancient Egyptian king Ka, an early ruler of the First Dynasty period.
  • D. Waset
    Waset was the ancient Egyptian city known in Greek as Thebes, a major religious and political center along the Nile.
  • E. Asungor
    Asungor is an alternative name for the Sungor language, a Nilo-Saharan language spoken by the Sungor people of Chad and Sudan.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a127b2688190ae3a340f851e834b completed April 10, 2026, 7:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69ee87922b308190a16d026a75b1043e completed April 26, 2026, 9:45 p.m.
Created at: April 8, 2026, 9:39 p.m.