Triple
T1915717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah Ya-Sin |
E40012
|
entity |
| Predicate | recitedOnOccasion |
P33123
|
FINISHED |
| Object | funerals |
—
|
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: funerals | Statement: [Surah Ya-Sin, recitedOnOccasion, funerals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recitedOnOccasion Context triple: [Surah Ya-Sin, recitedOnOccasion, funerals]
-
A.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
-
B.
commemoratesEventDescribedIn
Indicates that something serves to honor or remember an event that is described in a particular source or representation.
-
C.
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.
-
D.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
E.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
- F. None of above. chosen
Provenance (4 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1e517e8819086e4bf5a305aeb25 |
completed | March 7, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1b180e481908bbe893d6ba6208b |
completed | March 7, 2026, 5:03 a.m. |
Created at: March 4, 2026, 7:35 p.m.