Triple
T7229297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ṣād |
E154862
|
entity |
| Predicate | muqattaʿatPosition |
P28358
|
FINISHED |
| Object | opening of Surah Ṣād |
—
|
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: opening of Surah Ṣād | Statement: [Ṣād, muqattaʿatPosition, opening of Surah Ṣād]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: muqattaʿatPosition Context triple: [Ṣād, muqattaʿatPosition, opening of Surah Ṣād]
-
A.
containsMuqattaat
chosen
Indicates that the referenced text or verse includes muqattaat, the disjointed or abbreviated Arabic letters that appear at the beginnings of some Quranic chapters.
-
B.
positionInKutubAlSittah
Indicates the specific placement or ordering of a text or hadith within the canonical six-book collection of Sunni hadith, known as Kutub al-Sittah.
-
C.
positionInMushaf
Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
-
D.
inAlMuwatta
Indicates that a referenced text, ruling, or narration is found within the Islamic legal compilation Al-Muwatta.
-
E.
quranPosition
Indicates the specific location or ordering of a referenced element within the text or structure of 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9e0ba248190a57a3b4fa8b858c7 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.