Triple

T37407890
Position Surface form Disambiguated ID Type / Status
Subject Al-Hashr E929180 entity
Predicate finalVersesKnownFor P199139 FINISHED
Object Enumeration of several divine names 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: Enumeration of several divine names | Statement: [Al-Hashr, finalVersesKnownFor, Enumeration of several divine names]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: finalVersesKnownFor
Context triple: [Al-Hashr, finalVersesKnownFor, Enumeration of several divine names]
  • A. containsVerse
    Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
  • B. commonlyPerformedVerses
    Indicates that certain verses are frequently performed or recited in practice, relative to others.
  • C. hasVersesBy
    Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
  • D. hasVersesIn
    Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
  • E. verses
    Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
  • F. None of above. chosen

Provenance (4 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_69f76ebbf79c8190b85bbcf3a6be57e4 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff21cbd9108190a52c0ba42004c669 completed May 9, 2026, noon
PD Predicate disambiguation batch_69ff1faea91881908c626c70bca5100a completed May 9, 2026, 11:51 a.m.
PDg Predicate description generation batch_69ff21ca6964819088bdf1810b7863f2 completed May 9, 2026, noon
Created at: May 3, 2026, 4:16 p.m.