Triple
T34474349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamic inquisition |
E884988
|
entity |
| Predicate | endedByPolicyChange |
P103024
|
FINISHED |
| Object | reversal of support for Mu'tazilism |
—
|
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: reversal of support for Mu'tazilism | Statement: [Islamic inquisition, endedByPolicyChange, reversal of support for Mu'tazilism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedByPolicyChange Context triple: [Islamic inquisition, endedByPolicyChange, reversal of support for Mu'tazilism]
-
A.
imposedPolicyChange
Indicates that one entity has unilaterally enforced a modification to rules, procedures, or policies upon another entity or system.
-
B.
endedPolicy
chosen
Indicates that a previously active policy has been brought to an end or terminated.
-
C.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
D.
hasPolicyChange
Indicates that a change has been made to an existing policy or set of policies affecting the related entities.
-
E.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.