Triple
T24282448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharh Muntaha al-Iradat |
E605581
|
entity |
| Predicate | legalMadhhab |
P52406
|
FINISHED |
| Object | Hanbali |
—
|
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: Hanbali | Statement: [Sharh Muntaha al-Iradat, legalMadhhab, Hanbali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalMadhhab Context triple: [Sharh Muntaha al-Iradat, legalMadhhab, Hanbali]
-
A.
religiousJurisdiction
Indicates that one entity holds official religious authority or governance over another entity or area.
-
B.
fiqhScope
Indicates the domain or scope within Islamic jurisprudence (fiqh) to which a particular ruling, issue, or concept applies.
-
C.
fiqh
Indicates the relationship of deriving, applying, or adhering to Islamic legal rulings and jurisprudential judgments regarding actions or situations.
-
D.
religiousLawView
Indicates a person's stance, interpretation, or opinion regarding a particular religious law or set of religious legal principles.
-
E.
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.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f52e57c8190ab73e4b2b6a9eafd |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.