Triple
T9984234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 29:69 |
E196525
|
entity |
| Predicate | positionInSurah |
P50394
|
FINISHED |
| Object | final verse of Surah Al-Ankabut |
—
|
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: final verse of Surah Al-Ankabut | Statement: [Quran 29:69, positionInSurah, final verse of Surah Al-Ankabut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSurah Context triple: [Quran 29:69, positionInSurah, final verse of Surah Al-Ankabut]
-
A.
quranPosition
chosen
Indicates the specific location or ordering of a referenced element within the text or structure of the Quran.
-
B.
commandInSurah
Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
-
C.
sajdahVerseNumber
Indicates the verse number in a chapter at which a prostration (sajdah) is prescribed or occurs.
-
D.
positionInMushaf
Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
-
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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8bdc0388190bbbd4bdc5ac3adec |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:49 p.m.