Triple
T32752092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | غافر |
E837524
|
entity |
| Predicate | hasQuranicForm |
P73712
|
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: [غافر, hasQuranicForm, غَافِرِ الذَّنْبِ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuranicForm Context triple: [غافر, hasQuranicForm, غَافِرِ الذَّنْبِ]
-
A.
hasQuranicEquivalent
Indicates that something has a corresponding or analogous concept, term, or passage found in the Quran.
-
B.
hasQuranicDescription
Indicates that there exists a description or characterization of the subject that is explicitly given or referenced in the Quran.
-
C.
hasGivenNameFormInArabic
chosen
Indicates that an entity has a specific given-name form expressed in the Arabic language.
-
D.
hasQuranicVerseReference
Indicates that an entity is associated with, or refers to, a specific verse or verses from the Quran.
-
E.
containsMuqattaat
Indicates that the referenced text or verse includes muqattaat, the disjointed or abbreviated Arabic letters that appear at the beginnings of some Quranic chapters.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.