Triple
T6531642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Household of Muhammad |
E152243
|
entity |
| Predicate | hasQuranicReference |
P16948
|
FINISHED |
| Object | Quran 33:33 |
—
|
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 33:33 | Statement: [Household of Muhammad, hasQuranicReference, Quran 33:33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuranicReference Context triple: [Household of Muhammad, hasQuranicReference, Quran 33:33]
-
A.
quranicSurahMention
chosen
Indicates that a specific Quranic surah is mentioned, referenced, or cited in relation to another entity or context.
-
B.
quranicStatus
Indicates the status or classification of something in relation to its recognition, treatment, or role within the Quran.
-
C.
isAssociatedWithReligiousText
Indicates a relationship where an entity is connected or linked in some way to a religious text, such as being based on, derived from, or directly related to it.
-
D.
quranicVerse
Indicates that a given text segment is a verse from the Quran and encodes the relationship between that verse and its source scripture.
-
E.
containsMadaniVerses
Indicates that the subject includes or is composed of verses classified as Madani (revealed in Medina).
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adbcf820819097ca33a5fc14fd64 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.