Triple
T24282558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ala’ al-Din Ali ibn Sulayman al-Mardawi |
E605583
|
entity |
| Predicate | jurisprudentialRole |
P5610
|
FINISHED |
| Object | mufti |
—
|
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: mufti | Statement: [Ala’ al-Din Ali ibn Sulayman al-Mardawi, jurisprudentialRole, mufti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisprudentialRole Context triple: [Ala’ al-Din Ali ibn Sulayman al-Mardawi, jurisprudentialRole, mufti]
-
A.
deJureRole
Indicates that an entity holds a role or position by law or formal right, regardless of whether it is exercised in practice.
-
B.
judicialRole
Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
-
C.
legalSystemRole
Indicates the specific function, capacity, or position an entity holds within a legal or judicial system.
-
D.
legalProfessionRole
chosen
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
E.
courtRole
Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
- 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.