Triple

T31335875
Position Surface form Disambiguated ID Type / Status
Subject مزدلفة E799170 entity
Predicate hasExceptionRule P181446 FINISHED
Object يجوز للضعفة والنساء والمرضى الدفع منها إلى منى بعد منتصف الليل 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: يجوز للضعفة والنساء والمرضى الدفع منها إلى منى بعد منتصف الليل | Statement: [مزدلفة, hasExceptionRule, يجوز للضعفة والنساء والمرضى الدفع منها إلى منى بعد منتصف الليل]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExceptionRule
Context triple: [مزدلفة, hasExceptionRule, يجوز للضعفة والنساء والمرضى الدفع منها إلى منى بعد منتصف الليل]
  • A. hasExceptionFor
    Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
  • B. hasException
    Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
  • C. hasExceptionType
    Indicates that a given entity is associated with, or categorized by, a specific type of exception.
  • D. hasRule
    Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
  • E. hasRuleFor
    Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
  • 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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f7764ab1fc81909f9348db87bd7692 completed May 3, 2026, 4:22 p.m.
PD Predicate disambiguation batch_69f76905d9c88190b1ee810bc9ab644f completed May 3, 2026, 3:25 p.m.
PDg Predicate description generation batch_69f77648979c8190b6cdbb835ab8987c completed May 3, 2026, 4:22 p.m.
Created at: April 29, 2026, 9:16 p.m.