Triple

T14898408
Position Surface form Disambiguated ID Type / Status
Subject Iunet-ta-netert E359937 entity
Predicate hasRitualFeature P40534 FINISHED
Object birth house (mammisi) 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: birth house (mammisi) | Statement: [Iunet-ta-netert, hasRitualFeature, birth house (mammisi)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRitualFeature
Context triple: [Iunet-ta-netert, hasRitualFeature, birth house (mammisi)]
  • A. hasRitual
    Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
  • B. hasRitualElements chosen
    Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
  • C. hasRituals
    Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
  • D. hasRitualRule
    Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
  • E. hasRitualFocus
    Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
  • 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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded6084574819098033a9723f3e1c4 completed April 15, 2026, 12:04 a.m.
PD Predicate disambiguation batch_69de9a4a14a88190951bb8f4c60bd37b completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:11 a.m.