Triple
T12428895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An-Nazi'at |
E296970
|
entity |
| Predicate | chapterOrderInMushaf |
P26532
|
FINISHED |
| Object | 79 |
—
|
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: 79 | Statement: [An-Nazi'at, chapterOrderInMushaf, 79]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chapterOrderInMushaf Context triple: [An-Nazi'at, chapterOrderInMushaf, 79]
-
A.
chronologicalOrderOfFullSurah
Indicates the sequential position of a complete surah within an ordered timeline or arrangement.
-
B.
positionInMushaf
chosen
Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
-
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.
kuficOrder
Indicates that one entity commissions, arranges, or prescribes the creation or use of Kufic script in relation to another entity.
-
E.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.