Triple
T6517905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salah in Islam |
E148309
|
entity |
| Predicate | specialWeeklyPrayer |
P21327
|
FINISHED |
| Object | Jumuah prayer |
—
|
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: Jumuah prayer | Statement: [Salah in Islam, specialWeeklyPrayer, Jumuah prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialWeeklyPrayer Context triple: [Salah in Islam, specialWeeklyPrayer, Jumuah prayer]
-
A.
prayerIntention
Indicates that one entity directs a prayer or spiritual request specifically on behalf of, or concerning, another entity or situation.
-
B.
associatedPrayer
chosen
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
C.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
D.
devotionalDayCommon
Indicates that two or more entities share the same religious or spiritual day of devotion or observance.
-
E.
liturgicalMoment
Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.