Triple
T26172778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عبد القادر الجيلاني |
E654453
|
entity |
| Predicate | المذهب الفقهي |
P52406
|
FINISHED |
| Object | الحنبلي |
—
|
NE NERFINISHED |
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.
fiqh
Indicates the relationship of deriving, applying, or adhering to Islamic legal rulings and jurisprudential judgments regarding actions or situations.
-
B.
fiqhScope
Indicates the domain or scope within Islamic jurisprudence (fiqh) to which a particular ruling, issue, or concept applies.
-
C.
madhhab
chosen
Indicates the school of thought or legal tradition within a broader religious or jurisprudential system that an entity follows or is associated with.
-
D.
majorFiqhText
Indicates that a work is recognized as a primary or foundational text within the field of Islamic jurisprudence (fiqh).
-
E.
approachToUsulAlFiqh
Indicates the methodological stance or framework one adopts toward the principles and foundations of Islamic jurisprudence (uṣūl al-fiqh).
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c4485748190aff17798bca51406 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:36 p.m.