Triple
T9270161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | جبل عرفة |
E222803
|
entity |
| Predicate | أهمية دينية |
P2154
|
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: [جبل عرفة, أهمية دينية, يعد من أهم مشاعر الحج]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: أهمية دينية Context triple: [جبل عرفة, أهمية دينية, يعد من أهم مشاعر الحج]
-
A.
الديانة
Indicates the religious affiliation or faith tradition that an entity follows or is associated with.
-
B.
religiousElement
chosen
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
C.
religiousTextType
Indicates that one entity is a religious text and specifies the type or category of that religious text in relation to the other entity.
-
D.
regardedAsScriptureBy
Indicates that something is considered to be sacred scripture or canonical religious text by a particular person, group, or tradition.
-
E.
religiousTextOf
Indicates that one entity is a religious text that is sacred to, foundational for, or primarily associated with another entity (such as a religion, denomination, or faith community).
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078525308190abfb883123742d3f |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.