Triple
T36001751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | العرش |
E1041149
|
entity |
| Predicate | يُذكر_في_الأحاديث |
P89069
|
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.
ذُكر_في
chosen
Indicates that an entity is mentioned or referenced within another entity, such as a text, document, or source.
-
B.
hadithsNarrated
Indicates that one entity (typically a person) has narrated, transmitted, or reported the hadiths associated with another entity (such as a collection, text, or individual hadith).
-
C.
describedInHadithAs
Indicates that something is mentioned, characterized, or narrated within a hadith text.
-
D.
narratedHadith
Indicates that one entity transmitted or reported a hadith (a prophetic narration) from or about another entity.
-
E.
hasHadithReference
Indicates that there exists a reference or citation linking something to a specific hadith source or passage.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.