Triple
T26062095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushaf |
E657286
|
entity |
| Predicate | hasVariantReadingsOfQur’an |
P59286
|
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, hasVariantReadingsOfQur’an, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantReadingsOfQur’an Context triple: [Mushaf, hasVariantReadingsOfQur’an, Yes]
-
A.
hasVariantReadingsWith
chosen
Indicates a relationship where two textual items are linked because they exhibit differing or alternative readings of (typically) the same underlying content.
-
B.
qiraat
Indicates a recitation relationship, where one entity recites, chants, or reads aloud a text or passage.
-
C.
hasQuranicEquivalent
Indicates that something has a corresponding or analogous concept, term, or passage found in the Quran.
-
D.
qiraatTransmittedBy
Indicates that a particular Qur’anic recitation (qirāʾah) is transmitted or narrated through a specific transmitter or chain of transmitters.
-
E.
viewOnQuran
Indicates a relationship where an entity holds or expresses a particular stance, interpretation, or opinion regarding the Quran.
- 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_69f606941410819098a15b288273c3e1 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:18 p.m.