Triple

T29135336
Position Surface form Disambiguated ID Type / Status
Subject Mistress of Isheru E738498 entity
Predicate appliesToDeityInReligion P71453 FINISHED
Object ancient Egyptian religion 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: ancient Egyptian religion | Statement: [Mistress of Isheru, appliesToDeityInReligion, ancient Egyptian religion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesToDeityInReligion
Context triple: [Mistress of Isheru, appliesToDeityInReligion, ancient Egyptian religion]
  • A. appliesToDeityIn chosen
    Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
  • B. refersToDeityFunction
    Indicates that one entity denotes, describes, or points to the role, power, or functional aspect of a deity.
  • C. hasDeity
    Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
  • D. roleOfReferencedDeity
    Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
  • E. typeOfDeity
    Indicates that one entity is classified as a specific kind or category of deity in relation to another.
  • 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_69f07cb3adb48190a9e0e169cd026634 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69fd389cb28c819099a77e28d25f258a completed May 8, 2026, 1:13 a.m.
PD Predicate disambiguation batch_69fd3826d8048190ada79a5868d1d7f3 completed May 8, 2026, 1:11 a.m.
Created at: April 28, 2026, 11:34 a.m.