Triple
T9220525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maqasid al-Shariah |
E221347
|
entity |
| Predicate | classifiesInterest |
P77216
|
FINISHED |
| Object | daruriyyat (essentials) |
—
|
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: daruriyyat (essentials) | Statement: [Maqasid al-Shariah, classifiesInterest, daruriyyat (essentials)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiesInterest Context triple: [Maqasid al-Shariah, classifiesInterest, daruriyyat (essentials)]
-
A.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
interestType
chosen
Indicates the specific category or nature of interest that one entity has in relation to another or to a subject.
-
C.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
-
D.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
E.
representsInterestOf
Indicates that one entity expresses, holds, or embodies an interest, concern, or stake in another entity or subject.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda75b6888190814cfb890e763b8f |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.