Triple
T14436727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سورة الهمزة |
E357981
|
entity |
| Predicate | ترتبط بسورة |
P30312
|
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.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
B.
associatedWithBiblicalChapter
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
C.
followsSurah
chosen
Indicates that one surah directly comes after or is ordered immediately following another surah in a specified sequence.
-
D.
isAssociatedWithReligiousText
Indicates a relationship where an entity is connected or linked in some way to a religious text, such as being based on, derived from, or directly related to it.
-
E.
لغة السورة
Indicates the language in which a given surah (chapter of the Qur’an) is expressed or written.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.