Triple
T37699153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMI All Share Index |
E939009
|
entity |
| Predicate | isShariahCompliant |
P189151
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [KMI All Share Index, isShariahCompliant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShariahCompliant Context triple: [KMI All Share Index, isShariahCompliant, true]
-
A.
hasRulingInFiqh
Indicates that a subject has an associated legal ruling or judgment within the framework of Islamic jurisprudence (fiqh).
-
B.
isPillarOfIslam
Indicates that something is one of the fundamental obligatory practices that constitute the core pillars of Islam.
-
C.
declaresShariaAs
Indicates that an authority or document formally designates or proclaims something to be governed by, based on, or in accordance with Sharia (Islamic law).
-
D.
statusInIslamicTradition
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
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. chosen
Provenance (4 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.