Triple
T37349505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الممتحنة |
E927282
|
entity |
| Predicate | بعدها_في_المصحف |
P117038
|
FINISHED |
| Object | سورة الصف |
—
|
NE NERFINISHED |
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.
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).
-
B.
تليها في المصحف
chosen
Indicates that one Quranic surah or verse comes immediately after another in the written order of the Mushaf.
-
C.
followsSurah
Indicates that one surah directly comes after or is ordered immediately following another surah in a specified sequence.
-
D.
مصحفياً
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.
-
E.
quranicDerivative
Indicates that one entity is a linguistic form or term derived from, based on, or morphologically related to a word or concept found in 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.