Triple
T25860956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | أهل السنة والجماعة |
E651475
|
entity |
| Predicate | يستندون_في_الفقه_إلى |
P107948
|
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.
fiqhScope
Indicates the domain or scope within Islamic jurisprudence (fiqh) to which a particular ruling, issue, or concept applies.
-
B.
approachToUsulAlFiqh
chosen
Indicates the methodological stance or framework one adopts toward the principles and foundations of Islamic jurisprudence (uṣūl al-fiqh).
-
C.
hasRulingInFiqh
Indicates that a subject has an associated legal ruling or judgment within the framework of Islamic jurisprudence (fiqh).
-
D.
fiqh
Indicates the relationship of deriving, applying, or adhering to Islamic legal rulings and jurisprudential judgments regarding actions or situations.
-
E.
religiousAuthorityBasis
Indicates the foundational source or justification upon which a religious authority’s legitimacy or power is based.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:05 a.m.