Triple
T34852318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sundering |
E1004629
|
entity |
| Predicate | positionWithinMushaf |
P26532
|
FINISHED |
| Object | After Surah Al-Mutaffifin |
—
|
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: After Surah Al-Mutaffifin | Statement: [The Sundering, positionWithinMushaf, After Surah Al-Mutaffifin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinMushaf Context triple: [The Sundering, positionWithinMushaf, After Surah Al-Mutaffifin]
-
A.
positionInMushaf
chosen
Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
-
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.
quranPosition
Indicates the specific location or ordering of a referenced element within the text or structure of the Quran.
-
D.
hasPageRangeInMushaf
Indicates that a text segment spans a specific range of pages within a particular mushaf (written copy of the Quran).
-
E.
positionInPage
Indicates the specific location or placement of an element within a page’s layout or structure.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4 p.m.