Triple
T2049769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Al-Ahqaf |
E45537
|
entity |
| Predicate | verseRangeForJinnStory |
P27216
|
FINISHED |
| Object | 31–32 |
—
|
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: 31–32 | Statement: [Surah Al-Ahqaf, verseRangeForJinnStory, 31–32]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verseRangeForJinnStory Context triple: [Surah Al-Ahqaf, verseRangeForJinnStory, 31–32]
-
A.
hasJuzRange
Indicates that an entity (such as a text or passage) spans, is associated with, or falls within a specified range of Juz segments.
-
B.
hasVerseRange
chosen
Indicates a relationship where a text or passage is associated with a specific contiguous range of verses it spans.
-
C.
bookChapterRange
Indicates a relationship where a specified range of chapters within a book is identified or referenced as a contiguous segment.
-
D.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
introducedRange
Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98e10d48190bb96cd1f8ea3c08b |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.