Triple
T25814805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | غار النبي |
E650218
|
entity |
| Predicate | الأهمية الدينية |
P86931
|
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 a religious origin or affiliation that an entity belongs to or is derived from.
-
B.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
C.
devotionalImportance
chosen
Indicates the degree to which something is regarded as significant or central within acts of devotion, worship, or religious practice.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
hasReligiousSignificanceVia
Indicates that something holds religious significance specifically by means of, or through the mediation of, another entity, event, or context.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c84ac4819091492e52a5a8b873 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:25 a.m.