Triple
T37349503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الممتحنة |
E927282
|
entity |
| Predicate | مصحف |
P178492
|
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.
حكم تلاوتها
Indicates the ruling or legal judgment regarding the recitation of something (e.g., whether its recitation is obligatory, recommended, permissible, disliked, or forbidden).
-
C.
عدد السجدات
Indicates the number of prostrations performed in a given prayer or worship context.
-
D.
جمع_المصحف
chosen
Indicates the action of compiling or collecting the Qur’anic text into a single, organized written mushaf.
-
E.
מאפיין לוח
Indicates a relationship where something serves as a characteristic, property, or defining feature of a board.
- 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.