Triple
T34905929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الحاقة |
E1006724
|
entity |
| Predicate | موقعها في المصحف |
P26532
|
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 one Quranic surah or verse comes immediately after another in the written order of the Mushaf.
-
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 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.
positionInMushaf
chosen
Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
-
E.
positionInMishnehTorah
Indicates the specific location or ordering of a given item within the structure of the Mishneh Torah 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.