Triple
T33946701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 54:2 |
E870309
|
entity |
| Predicate | canonicalMushafOrder |
P114903
|
FINISHED |
| Object | 54:2 |
—
|
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: 54:2 | Statement: [Quran 54:2, canonicalMushafOrder, 54:2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalMushafOrder Context triple: [Quran 54:2, canonicalMushafOrder, 54:2]
-
A.
kuficOrder
Indicates that one entity commissions, arranges, or prescribes the creation or use of Kufic script in relation to another entity.
-
B.
hasCanonicalOrderInQuran
chosen
Indicates that there is a specific, officially recognized sequence or position of something within the canonical ordering of the Quran.
-
C.
revealedInArabicOrder
Indicates that something was disclosed or made known following the original sequence in which it was revealed in Arabic.
-
D.
ordersSurahsPrimarilyBy
Indicates that one entity arranges or sequences surahs chiefly according to a specified organizing principle or criterion.
-
E.
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).
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.