Triple
T15183428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الكوثر |
E362805
|
entity |
| Predicate | تليها في المصحف |
P117038
|
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 that someone is acting in the capacity of a Qur’an specialist or is engaged in work related to the writing, editing, or production of the Qur’anic text.
-
B.
foundInMushaf
Indicates that something (such as a verse, phrase, or reading) is present and recorded in the written text of the Mushaf (the compiled Qur’anic codex).
-
C.
حكم تلاوتها
Indicates the ruling or legal judgment regarding the recitation of something (e.g., whether its recitation is obligatory, recommended, permissible, disliked, or forbidden).
-
D.
لغة السورة
Indicates the language in which a given surah (chapter of the Qur’an) is expressed or written.
-
E.
inAlMuwatta
Indicates that a referenced text, ruling, or narration is found within the Islamic legal compilation Al-Muwatta.
- F. None of above. chosen
Provenance (4 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.