Triple
T37699114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMI-30 Index |
E939008
|
entity |
| Predicate | religiousCompliance |
P6166
|
FINISHED |
| Object | Islamic Shariah |
—
|
NE NERFINISHED |
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: Islamic Shariah | Statement: [KMI-30 Index, religiousCompliance, Islamic Shariah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCompliance Context triple: [KMI-30 Index, religiousCompliance, Islamic Shariah]
-
A.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
B.
religiousTextStatus
Indicates the status or role that a text holds within a religious tradition, such as whether it is considered sacred, canonical, apocryphal, or otherwise classified.
-
C.
religiousRestriction
chosen
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
-
D.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
E.
reveredByReligion
Indicates that a religion holds a particular entity in high esteem, veneration, or sacred regard.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:18 p.m.