Triple

T19303763
Position Surface form Disambiguated ID Type / Status
Subject Usermaatre-Meryamun E482767 entity
Predicate component P35 FINISHED
Object Meryamun NE NERFINISHED

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: Meryamun | Statement: [Usermaatre-Meryamun, component, Meryamun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meryamun
Context triple: [Usermaatre-Meryamun, component, Meryamun]
  • A. Senenmut
    Senenmut was a prominent ancient Egyptian official and architect of the 18th Dynasty, best known for his close association with Pharaoh Hatshepsut and for designing some of her most famous monuments.
  • B. Meryibre Khety
    Meryibre Khety was a pharaoh of ancient Egypt’s First Intermediate Period, ruling during the Tenth Dynasty from Herakleopolis.
  • C. Nekheb
    Nekheb was an ancient Egyptian city in Upper Egypt, closely associated with the vulture goddess Nekhbet and serving as an important religious and political center.
  • D. Nebmaatre-Meryamun chosen
    Nebmaatre-Meryamun is the throne name of the ancient Egyptian pharaoh Ramesses VI of the Twentieth Dynasty.
  • E. Renseneb
    Renseneb was a relatively obscure pharaoh of ancient Egypt’s 13th Dynasty, ruling briefly during the politically unstable Second Intermediate Period.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604c5903c819090b3f89c3f33b005 completed April 20, 2026, 10:49 a.m.
Created at: April 10, 2026, 1:31 p.m.