Triple

T34754796
Position Surface form Disambiguated ID Type / Status
Subject record of the wicked (Sijjin) E1001887 entity
Predicate QuranChapterReference P16948 FINISHED
Object Qur’an 83:7–9 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: Qur’an 83:7–9 | Statement: [record of the wicked (Sijjin), QuranChapterReference, Qur’an 83:7–9]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: QuranChapterReference
Context triple: [record of the wicked (Sijjin), QuranChapterReference, Qur’an 83:7–9]
  • A. quranSection
    Indicates that one entity is a section, passage, or subdivided part of the Quran associated with another entity.
  • B. quranicSurahMention chosen
    Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
  • C. commandInSurah
    Indicates that a particular command or directive appears within a specified surah (chapter) of the Quran.
  • D. quranManzil
    Indicates a relationship where a portion of the Quran is assigned or associated as a specific “manzil” (section) for recitation or division purposes.
  • E. chapterAndVerse
    Indicates a relationship where a specific chapter is associated with a specific verse (or set of verses) within a structured text, such as a book or document.
  • 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_69f76db0fb30819096709d43f9a1f45f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7817daf00819098936402e75ab0a6 completed May 3, 2026, 5:10 p.m.
PD Predicate disambiguation batch_69f780fc5ed88190b7200ee5a29940af completed May 3, 2026, 5:08 p.m.
Created at: May 3, 2026, 3:59 p.m.