Triple
T30481299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | آل سعود |
E775594
|
entity |
| Predicate | الفرع الفقهي الغالب |
P52406
|
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 doctrinal or jurisprudential school to which an entity is affiliated or adheres.
-
B.
majorFiqhText
Indicates that a work is recognized as a primary or foundational text within the field of Islamic jurisprudence (fiqh).
-
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.
approachToUsulAlFiqh
Indicates the methodological stance or framework one adopts toward the principles and foundations of Islamic jurisprudence (uṣūl al-fiqh).
-
E.
fiqh
Indicates the relationship of deriving, applying, or adhering to Islamic legal rulings and jurisprudential judgments regarding actions or situations.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687415610819081818d08f7c79a81 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:12 p.m.