Triple
T14550182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Clot |
E341394
|
entity |
| Predicate | hasOpeningWordsArabic |
P114900
|
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: [The Clot, hasOpeningWordsArabic, اقْرَأْ بِاسْمِ رَبِّكَ الَّذِي خَلَقَ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningWordsArabic Context triple: [The Clot, hasOpeningWordsArabic, اقْرَأْ بِاسْمِ رَبِّكَ الَّذِي خَلَقَ]
-
A.
hasNameInArabic
Indicates that an entity is associated with a specific name expressed in the Arabic language.
-
B.
hasGivenNameFormInArabic
Indicates that an entity has a specific given-name form expressed in the Arabic language.
-
C.
openingWordsHebrew
Indicates that the specified words are the opening (initial) words of a text or passage in Hebrew.
-
D.
revealedInArabicOrder
Indicates that something was disclosed or made known following the original sequence in which it was revealed in Arabic.
-
E.
containsMuqattaat
Indicates that the referenced text or verse includes muqattaat, the disjointed or abbreviated Arabic letters that appear at the beginnings of some Quranic chapters.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ed2b4c8190945bd26531c71f1f |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:23 a.m.