Triple

T11629178
Position Surface form Disambiguated ID Type / Status
Subject Piye E276350 entity
Predicate sibling P363 FINISHED
Object Amenirdis I E664655 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: Amenirdis I | Statement: [Piye, sibling, Amenirdis I]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amenirdis I
Context triple: [Piye, sibling, Amenirdis I]
  • A. Amenirdis I chosen
    Amenirdis I was a Kushite princess of the 25th Dynasty who served as Divine Adoratrice of Amun in Thebes, wielding significant religious and political power in ancient Egypt.
  • B. Mereret
    Mereret was an ancient Egyptian princess of the 12th Dynasty, likely a royal daughter associated with the reign of Pharaoh Amenemhat III.
  • C. Khemenu
    Khemenu was an ancient Egyptian city, better known by its Greek name Hermopolis, that served as a major religious center dedicated to the god Thoth.
  • D. Itaweret
    Itaweret was an ancient Egyptian queen of the 12th Dynasty, known as the consort of Pharaoh Senusret II and likely the mother of his heir.
  • E. Khentkaus I
    Khentkaus I was an influential ancient Egyptian queen of the 4th–5th Dynasty transition, often associated with Giza and thought to have held an unusually powerful, possibly kingly, status.
  • 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_69f4171833948190adafe71ab0d9d2de completed May 1, 2026, 2:59 a.m.
Created at: April 8, 2026, 9:39 p.m.