Triple

T14481376
Position Surface form Disambiguated ID Type / Status
Subject Meryatum E359108 entity
Predicate sibling P363 FINISHED
Object Amun-her-khepeshef E362898 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: Amun-her-khepeshef | Statement: [Meryatum, sibling, Amun-her-khepeshef]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amun-her-khepeshef
Context triple: [Meryatum, sibling, Amun-her-khepeshef]
  • A. Amun-her-khepeshef chosen
    Amun-her-khepeshef was a crown prince of ancient Egypt’s 19th Dynasty and the eldest son and heir apparent of Pharaoh Ramesses II.
  • B. Khnum
    Khnum is an ancient Egyptian ram-headed god associated with the Nile’s inundation, creation, and the molding of human beings on a potter’s wheel.
  • C. Djedkheperew
    Djedkheperew was a relatively obscure pharaoh of Egypt’s 13th Dynasty, known primarily from limited archaeological and textual evidence dating to the early Second Intermediate Period.
  • D. Amun
    Amun is a major ancient Egyptian deity, often associated with the sun and creation and later merged with Ra as Amun-Ra, who became one of the chief gods of the Egyptian pantheon.
  • E. Menkheperure
    Menkheperure is the throne name of Pharaoh Thutmose IV, an 18th Dynasty ruler of ancient Egypt.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de924bc548819087a2f693840d7426 completed April 14, 2026, 7:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd64a41a8c819081a3eaabbe66577a completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:20 a.m.