Triple

T1473367
Position Surface form Disambiguated ID Type / Status
Subject Battle of Badr E27185 entity
Predicate quranicReference P16948 FINISHED
Object Quran 3:123–125 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: Quran 3:123–125 | Statement: [Battle of Badr, quranicReference, Quran 3:123–125]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: quranicReference
Context triple: [Battle of Badr, quranicReference, Quran 3:123–125]
  • A. quranicVerse
    Indicates that a given text segment is a verse from the Quran and encodes the relationship between that verse and its source scripture.
  • B. quranicSurahMention chosen
    Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
  • C. quranicSurah
    Indicates that one entity is a chapter (surah) of the Quran associated with or identified by the other entity.
  • D. quranSurahNumber
    Indicates the numerical position or identifier assigned to a specific surah (chapter) within the Quran.
  • E. sajdahVerseNumber
    Indicates the verse number in a chapter at which a prostration (sajdah) is prescribed or occurs.
  • 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_69a496d25d6881909dbd84f86d763992 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c5ff8dbc81909eafcfc9f2260a22 completed March 1, 2026, 11:04 p.m.
PD Predicate disambiguation batch_69a4c48350d88190a81bd149103f93e3 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:01 p.m.