Triple
T7225111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghar Hira |
E150358
|
entity |
| Predicate | notObligatoryIn |
P71358
|
FINISHED |
| Object | Hajj rituals |
—
|
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: Hajj rituals | Statement: [Ghar Hira, notObligatoryIn, Hajj rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notObligatoryIn Context triple: [Ghar Hira, notObligatoryIn, Hajj rituals]
-
A.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
B.
notObligatoryInMajorityView
chosen
Indicates that, according to the majority view or ruling, the action or relationship in question is not considered obligatory.
-
C.
notObligatoryHolyDayOfObligation
Indicates that a particular holy day is explicitly not classified as a Holy Day of Obligation.
-
D.
notGuaranteed
Indicates that the specified outcome, condition, or obligation is not assured to occur or be fulfilled.
-
E.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.