Triple

T7202452
Position Surface form Disambiguated ID Type / Status
Subject Ayat al-Kursi E148579 entity
Predicate foundInMushafOrder P26532 FINISHED
Object page containing Surah al-Baqarah verse 255 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: page containing Surah al-Baqarah verse 255 | Statement: [Ayat al-Kursi, foundInMushafOrder, page containing Surah al-Baqarah verse 255]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: foundInMushafOrder
Context triple: [Ayat al-Kursi, foundInMushafOrder, page containing Surah al-Baqarah verse 255]
  • A. positionInMushaf chosen
    Indicates the specific location or ordering of a text segment within the physical or canonical arrangement of the Mushaf (written Qur’an).
  • B. occursInSurah
    Indicates that something (such as a verse, concept, or event) takes place within or is contained in a specific surah.
  • C. hasPageRangeInMushaf
    Indicates that a text segment spans a specific range of pages within a particular mushaf (written copy of the Quran).
  • D. quranPosition
    Indicates the specific location or ordering of a referenced element within the text or structure of the Quran.
  • E. positionInMishnahOrders
    Indicates the specific ordinal position that something occupies within the sequence of Mishnah orders.
  • 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_69c687e8cf188190b5f3ecffd681f04e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e94a9ee4819086de79fcdfa1836a completed March 27, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69c6e757fed4819091b0a096e3befc3a completed March 27, 2026, 8:23 p.m.
Created at: March 27, 2026, 2:52 p.m.