Triple
T7225129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qur’an 96:1 |
E150359
|
entity |
| Predicate | openingWordsArabic |
P50395
|
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: [Qur’an 96:1, openingWordsArabic, اقْرَأْ بِاسْمِ رَبِّكَ الَّذِي خَلَقَ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingWordsArabic Context triple: [Qur’an 96:1, openingWordsArabic, اقْرَأْ بِاسْمِ رَبِّكَ الَّذِي خَلَقَ]
-
A.
openingWordsHebrew
Indicates that the specified words are the opening (initial) words of a text or passage in Hebrew.
-
B.
verseTextArabic
chosen
Indicates the Arabic-language text content associated with a specific verse in a scriptural or poetic work.
-
C.
revealedInArabicOrder
Indicates that something was disclosed or made known following the original sequence in which it was revealed in Arabic.
-
D.
openingVerb
Indicates that an entity performs the initial or primary action that begins an event, process, or interaction.
-
E.
translationOfOpeningWords
Indicates that one text is a translation of the initial words or opening phrase of another text.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.