Triple
T34455368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المجادلة |
E884489
|
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.
تليها في المصحف
chosen
Indicates that one Quranic surah or verse comes immediately after another in the written order of the Mushaf.
-
B.
جمع_المصحف
Indicates the action of compiling or collecting the Qur’anic text into a single, organized written mushaf.
-
C.
مصحفياً
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.
-
D.
hasCanonicalOrderInQuran
Indicates that there is a specific, officially recognized sequence or position of something within the canonical ordering of the Quran.
-
E.
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).
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71976c49c8190943046a0ff8950cb |
completed | May 3, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.