Triple
T11323700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Divorce |
E268154
|
entity |
| Predicate | hasPositionInMushaf |
P26532
|
FINISHED |
| Object | after Surah At-Taghabun |
—
|
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 At-Taghabun | Statement: [The Divorce, hasPositionInMushaf, after Surah At-Taghabun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInMushaf Context triple: [The Divorce, hasPositionInMushaf, after Surah At-Taghabun]
-
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.
hasPageRangeInMushaf
Indicates that a text segment spans a specific range of pages within a particular mushaf (written copy of the Quran).
-
C.
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).
-
D.
hasPositionInBook
Indicates that an entity occupies a specific position or location within a book.
-
E.
positionInGuruGranthSahib
Indicates the specific location or ordering of a referenced element within the text of the Guru Granth Sahib.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.