Triple

T19497108
Position Surface form Disambiguated ID Type / Status
Subject Procession of Sokar at Memphis E487797 entity
Predicate hasRitualParticipants P136136 FINISHED
Object priests of Sokar 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: priests of Sokar | Statement: [Procession of Sokar at Memphis, hasRitualParticipants, priests of Sokar]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRitualParticipants
Context triple: [Procession of Sokar at Memphis, hasRitualParticipants, priests of Sokar]
  • A. hasRitual
    Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
  • B. hasRituals
    Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
  • C. hasRitualRoleIn
    Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
  • D. hasRitualStage
    Indicates that something is associated with, or occurs during, a particular stage within a ritual process.
  • E. hasRitualElements
    Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
  • F. None of above. chosen

Provenance (4 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_69d8e8d9d1c88190b01cd78b8be49384 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e634924e24819085cd61ba33c84570 completed April 20, 2026, 2:13 p.m.
PD Predicate disambiguation batch_69e4fd7bd25881908caa04eaef1f6718 completed April 19, 2026, 4:06 p.m.
PDg Predicate description generation batch_69e5004d3a708190a1c13c8f644f3926 completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 1:40 p.m.