Triple
T30969248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | صعيد عرفة |
E789044
|
entity |
| Predicate | religiousRuling |
P36007
|
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: [صعيد عرفة, religiousRuling, الوقوف فيه ركن من أركان الحج]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousRuling Context triple: [صعيد عرفة, religiousRuling, الوقوف فيه ركن من أركان الحج]
-
A.
religiousAuthorityBasis
Indicates the foundational source or justification upon which a religious authority’s legitimacy or power is based.
-
B.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
C.
hasRulingInFiqh
chosen
Indicates that a subject has an associated legal ruling or judgment within the framework of Islamic jurisprudence (fiqh).
-
D.
religiousLawView
Indicates a person's stance, interpretation, or opinion regarding a particular religious law or set of religious legal principles.
-
E.
religiousLawAspect
Indicates that one entity represents a specific aspect, dimension, or component of a religious law associated with another entity.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 29, 2026, 8:54 p.m.