Triple
T31002933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة فصلت |
E789987
|
entity |
| Predicate | تدعو إلى |
P106311
|
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.
exhortedTo
chosen
Indicates that one entity strongly urged, encouraged, or pressured another entity to perform a particular action or adopt a certain course of behavior.
-
B.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
C.
exhortedBy
Indicates that one entity is strongly urged, encouraged, or admonished to act or think in a certain way by another entity.
-
D.
challengeTo
Indicates that one entity issues a challenge or dare for another entity to face or respond to.
-
E.
invocationWord
Indicates that a specific word or phrase is used to call upon, activate, or summon an entity, power, or process.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.