Triple
T26309445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عام الحزن |
E661778
|
entity |
| Predicate | أثر_ديني |
P24045
|
FINISHED |
| Object | يُستشهد به في الخطب والمواعظ عن الصبر والابتلاء |
—
|
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: يُستشهد به في الخطب والمواعظ عن الصبر والابتلاء | Statement: [عام الحزن, أثر_ديني, يُستشهد به في الخطب والمواعظ عن الصبر والابتلاء]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: أثر_ديني Context triple: [عام الحزن, أثر_ديني, يُستشهد به في الخطب والمواعظ عن الصبر والابتلاء]
-
A.
أصل_ديني
Indicates a religious origin or affiliation that an entity belongs to or is derived from.
-
B.
اثر
Indicates a causal or influential relationship where one entity produces, changes, or leaves an impact on another.
-
C.
اثر
Indicates that one entity has an effect, influence, or impact on another entity.
-
D.
الموقف_الديني
Indicates a religious stance or position that an entity holds toward a belief, practice, or issue.
-
E.
theologicalEffect
chosen
Indicates the impact or consequence that an action, event, or state has within a theological or religious framework (e.g., on doctrine, salvation, sin, or divine-human relations).
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee64ce08190b9fbede178cc6f28 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:21 p.m.