Triple

T2019609
Position Surface form Disambiguated ID Type / Status
Subject Hijr Ismail E44073 entity
Predicate hasRitualRule P34542 FINISHED
Object tawaf must be performed outside Hijr Ismail 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: tawaf must be performed outside Hijr Ismail | Statement: [Hijr Ismail, hasRitualRule, tawaf must be performed outside Hijr Ismail]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRitualRule
Context triple: [Hijr Ismail, hasRitualRule, tawaf must be performed outside Hijr Ismail]
  • A. hasRitual
    Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
  • B. hasRitualSpace
    Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
  • C. hasRitualObject
    Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
  • D. 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.
  • E. hasRitualCalendar
    Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
  • 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_69a8891201bc8190aca837be6de41579 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb8cfa5c88190b55bce5db968665b completed March 7, 2026, 5:34 a.m.
PD Predicate disambiguation batch_69abb7a389408190a84a54856352f15b completed March 7, 2026, 5:29 a.m.
PDg Predicate description generation batch_69abb83e7888819096dc40275c77daff completed March 7, 2026, 5:31 a.m.
Created at: March 4, 2026, 7:38 p.m.