Triple
T33457554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الزمخشري |
E856817
|
entity |
| Predicate | المنهج_في_التفسير |
P157036
|
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.
نوع_التفسير
Indicates the specific type or category of interpretation being applied to something.
-
B.
منهج_في_مفردات_ألفاظ_القرآن
chosen
Indicates a methodological relationship focused on analyzing and explaining the vocabulary and individual words of the Qur’an.
-
C.
interpretationInIslam
Indicates the religious understanding, explanation, or doctrinal meaning of something specifically within the framework of Islamic belief and scholarship.
-
D.
له_شروح
Indicates that something (typically a text, concept, or work) has one or more explanations or commentaries associated with it.
-
E.
מאפיין פרשנות
Indicates that something characterizes or defines a particular interpretation.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4cff8c08190aecaabf722cf3891 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.