Triple
T12383713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bismillāh ir-Raḥmān ir-Raḥīm |
E295806
|
entity |
| Predicate | verseNumberInSurahAnNaml |
P18696
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Bismillāh ir-Raḥmān ir-Raḥīm, verseNumberInSurahAnNaml, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verseNumberInSurahAnNaml Context triple: [Bismillāh ir-Raḥmān ir-Raḥīm, verseNumberInSurahAnNaml, 30]
-
A.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
-
B.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
C.
verseNumber
chosen
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
-
D.
containsAyatAlKursiVerseNumber
Indicates that the referenced text or passage includes the specific verse number corresponding to Ayat al-Kursi.
-
E.
sajdahVerseNumber
Indicates the verse number in a chapter at which a prostration (sajdah) is prescribed or occurs.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fbc3f608190b0ee3c4f304a94db |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.