Triple
T36946809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yawm al-Jumu'ah |
E913935
|
entity |
| Predicate | replacesPrayer |
P30993
|
FINISHED |
| Object | Dhuhr prayer on Friday |
—
|
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: Dhuhr prayer on Friday | Statement: [Yawm al-Jumu'ah, replacesPrayer, Dhuhr prayer on Friday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesPrayer Context triple: [Yawm al-Jumu'ah, replacesPrayer, Dhuhr prayer on Friday]
-
A.
associatedPrayerChange
Indicates a change in a prayer that is linked or connected to another entity, event, or condition.
-
B.
replacesInPractice
chosen
Indicates that one entity has effectively taken over the role, function, or use of another entity in real-world application or usage.
-
C.
followsPrayer
Indicates that one event, action, or state occurs after and as a consequence of a prayer being made.
-
D.
prays
Indicates that one entity directs a prayer or act of worshipful communication toward another entity.
-
E.
praysFor
Indicates that one entity directs prayers or spiritual petitions on behalf of another entity.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.