Triple
T14719711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lam Yakun |
E345778
|
entity |
| Predicate | correspondsToAyah |
P93494
|
FINISHED |
| Object | Quran 98:1 opening words |
—
|
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: Quran 98:1 opening words | Statement: [Lam Yakun, correspondsToAyah, Quran 98:1 opening words]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToAyah Context triple: [Lam Yakun, correspondsToAyah, Quran 98:1 opening words]
-
A.
containsAyatAlKursiVerseNumber
Indicates that the referenced text or passage includes the specific verse number corresponding to Ayat al-Kursi.
-
B.
hasCanonicalOrderInQuran
Indicates that there is a specific, officially recognized sequence or position of something within the canonical ordering of the Quran.
-
C.
hasQuranicVerseReference
chosen
Indicates that an entity is associated with, or refers to, a specific verse or verses from the Quran.
-
D.
occursInSurah
Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
-
E.
quranManzil
Indicates a relationship where a portion of the Quran is assigned or associated as a specific “manzil” (section) for recitation or division purposes.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98823408190b4b58a4c4a3fa3a3 |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.