Triple

T26343766
Position Surface form Disambiguated ID Type / Status
Subject Qur'an 9:128 E662721 entity
Predicate characterizesProphetAs P176696 FINISHED
Object full of concern for the believers 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: full of concern for the believers | Statement: [Qur'an 9:128, characterizesProphetAs, full of concern for the believers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterizesProphetAs
Context triple: [Qur'an 9:128, characterizesProphetAs, full of concern for the believers]
  • A. regardsAsFinalProphet
    Indicates that one entity believes or treats another entity as the ultimate and last prophet, after whom no further prophets will come.
  • B. prophecyKnownAs
    Indicates that a particular prophecy is referred to or recognized by a specific name or title.
  • C. regardsAsOnlyProphetAfterMoses
    Indicates that one entity considers another entity to be the sole legitimate prophet following Moses.
  • D. roleInTheProphecy
    Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
  • E. regardsLeaderAsProphet
    Indicates that an individual views or treats their leader as a prophet, attributing prophetic authority or divine guidance to them.
  • 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_69ee81304194819092e20e0fae3aee07 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f6e6029a10819098ff21f58079e70e completed May 3, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69f6e3d5e8188190b1e1c2e5d1b77031 completed May 3, 2026, 5:57 a.m.
PDg Predicate description generation batch_69f6e60109648190947a64ca4ce81a3a completed May 3, 2026, 6:06 a.m.
Created at: April 26, 2026, 10:40 p.m.