Triple
T34754677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عِلِّيِّينَ |
E1001883
|
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.
نوع_التفسير
Indicates the specific type or category of interpretation being applied to something.
-
C.
foundInMushaf
Indicates that something (such as a verse, phrase, or reading) is present and recorded in the written text of the Mushaf (the compiled Qur’anic codex).
-
D.
viewInSunniSources
Indicates how something is regarded, interpreted, or evaluated specifically within Sunni Islamic sources or traditions.
-
E.
sourceOfHadithFor
Indicates that one entity serves as the originating source or transmitter for a particular hadith associated with another entity.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.