Triple
T32160606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qur’an 46:35 |
E821413
|
entity |
| Predicate | surahSequence |
P161846
|
FINISHED |
| Object | follows Qur’an 46:34 |
—
|
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: follows Qur’an 46:34 | Statement: [Qur’an 46:35, surahSequence, follows Qur’an 46:34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surahSequence Context triple: [Qur’an 46:35, surahSequence, follows Qur’an 46:34]
-
A.
chronologicalOrderOfFullSurah
Indicates the sequential position of a complete surah within an ordered timeline or arrangement.
-
B.
quranicSurah
Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
-
C.
revealedInSurahOrder
chosen
Indicates that a Quranic verse, passage, or concept was revealed according to a specific sequential position in the traditional order of surahs.
-
D.
surahApproximateOrderOfRevelation
Indicates the approximate chronological order in which a given surah was revealed relative to other surahs.
-
E.
quranSurahNumber
Indicates the numerical position or identifier assigned to a specific surah (chapter) within 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1a2d4c8190aa73a7b9b37c7c0d |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:32 a.m.