Triple
T1441853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Ar-Ra'd |
E31090
|
entity |
| Predicate | recitationUsedIn |
P25490
|
FINISHED |
| Object | Muslim prayer and worship |
—
|
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: Muslim prayer and worship | Statement: [Surah Ar-Ra'd, recitationUsedIn, Muslim prayer and worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recitationUsedIn Context triple: [Surah Ar-Ra'd, recitationUsedIn, Muslim prayer and worship]
-
A.
recitationRecommendedAfter
Indicates that one item is advised or suggested to be recited after another in a recommended sequence.
-
B.
recitationTradition
Indicates a relationship where a text, work, or content is transmitted or performed according to a particular established style, method, or lineage of recitation.
-
C.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
D.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usesCourse
Indicates that one entity makes use of, applies, or relies on a particular course in some context or activity.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.