Triple
T26062080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushaf |
E657286
|
entity |
| Predicate | hasFixedOrderOfSurahs |
P114903
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Mushaf, hasFixedOrderOfSurahs, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFixedOrderOfSurahs Context triple: [Mushaf, hasFixedOrderOfSurahs, Yes]
-
A.
hasCanonicalOrderInQuran
chosen
Indicates that there is a specific, officially recognized sequence or position of something within the canonical ordering of the Quran.
-
B.
ordersSurahsPrimarilyBy
Indicates that one entity arranges or sequences surahs chiefly according to a specified organizing principle or criterion.
-
C.
surahApproximateOrderOfRevelation
Indicates the approximate chronological order in which a given surah was revealed relative to other surahs.
-
D.
includeSurah
Indicates that one entity (such as a collection, book, or document) contains or incorporates a specific Surah as part of its contents.
-
E.
hasVerseOrder
Indicates that one verse is ordered or sequenced in relation to another verse within a structured 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 26, 2026, 7:18 p.m.