Triple

T27331996
Position Surface form Disambiguated ID Type / Status
Subject Hedjkheperre Setepenre E689826 entity
Predicate usedInRoyalProtocol P127798 FINISHED
Object full titulary of Shoshenq I LITERAL 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: full titulary of Shoshenq I | Statement: [Hedjkheperre Setepenre, usedInRoyalProtocol, full titulary of Shoshenq I]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInRoyalProtocol
Context triple: [Hedjkheperre Setepenre, usedInRoyalProtocol, full titulary of Shoshenq I]
  • A. royalUse chosen
    Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
  • B. usedAsRoyalFavor
    Indicates that something is employed or granted as a token of royal favor, privilege, or goodwill from a monarch or ruling authority.
  • C. ceremonialUse
    Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
  • D. royalFunction
    Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
  • E. ceremonialFeatures
    Indicates that something possesses attributes, elements, or characteristics specifically associated with ceremonies or ritual practices.
  • F. None of above.

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_69ef355e5b388190a8fc1eba9b4a6656 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 27, 2026, 11:38 a.m.