Triple
T14324063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-‘Asr |
E355168
|
entity |
| Predicate | isOftenRecitedIn |
P38181
|
FINISHED |
| Object | daily prayers |
—
|
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: daily prayers | Statement: [Al-‘Asr, isOftenRecitedIn, daily prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenRecitedIn Context triple: [Al-‘Asr, isOftenRecitedIn, daily prayers]
-
A.
isOftenRecitedFor
Indicates that something (such as a text, phrase, or piece of music) is frequently spoken, chanted, or performed for a particular purpose, audience, or occasion.
-
B.
recitedOnOccasion
Indicates that something (typically a text, speech, or performance) was recited during or in connection with a specific occasion or event.
-
C.
recites
Indicates that one entity verbally delivers or repeats from memory the words, text, or performance associated with another entity.
-
D.
alsoChantedIn
chosen
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
E.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883d1de88190a1e2bf2f1b692197 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.