Triple
T36427559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juz 26 |
E897343
|
entity |
| Predicate | containsSurahNumber |
P91803
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [Juz 26, containsSurahNumber, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSurahNumber Context triple: [Juz 26, containsSurahNumber, 47]
-
A.
includeSurah
chosen
Indicates that one entity (such as a collection, book, or document) contains or incorporates a specific Surah as part of its contents.
-
B.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
-
C.
containsAyatAlKursiVerseNumber
Indicates that the referenced text or passage includes the specific verse number corresponding to Ayat al-Kursi.
-
D.
numberOfSurahs
Indicates the total count of surahs associated with a given entity (such as a text, section, or collection).
-
E.
occursInSurah
Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
- 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
Created at: May 3, 2026, 4:10 p.m.