Triple
T25606405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 13:13 |
E641924
|
entity |
| Predicate | arabicKeyPhrase |
P114902
|
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: [Quran 13:13, arabicKeyPhrase, وَيُسَبِّحُ ٱلرَّعْدُ بِحَمْدِهِ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arabicKeyPhrase Context triple: [Quran 13:13, arabicKeyPhrase, وَيُسَبِّحُ ٱلرَّعْدُ بِحَمْدِهِ]
-
A.
hasKeyTermArabic
chosen
Indicates that an entity is associated with a specific key term expressed in the Arabic language.
-
B.
meaningInArabicRelatedForm
Indicates that one entity expresses the meaning of another entity in Arabic through a related or derived linguistic form.
-
C.
meaningInArabic
Indicates that one entity expresses the meaning or translation of another entity in the Arabic language.
-
D.
verseTextArabic
Indicates the Arabic-language text content associated with a specific verse in a scriptural or poetic work.
-
E.
quranicPhrase
Indicates that one entity is a phrase or expression that appears in, or is directly derived from, the Quran.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9aa9b6881909fd56b8a85534062 |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:38 p.m.