Triple
T30818642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharijite theology |
E784854
|
entity |
| Predicate | regardsAsUnbeliever |
P76739
|
FINISHED |
| Object | Muslim who commits major sin |
—
|
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: Muslim who commits major sin | Statement: [Kharijite theology, regardsAsUnbeliever, Muslim who commits major sin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardsAsUnbeliever Context triple: [Kharijite theology, regardsAsUnbeliever, Muslim who commits major sin]
-
A.
declaresUnbeliefOn
chosen
Indicates that one entity explicitly states or affirms a lack of belief in, or rejection of, another entity.
-
B.
viewOfUnbelief
Indicates a perspective, attitude, or interpretation that is characterized by disbelief or lack of faith toward something.
-
C.
isNonReligious
Indicates that an entity does not adhere to, practice, or identify with any religion or religious belief system.
-
D.
opposesDeity
Indicates a relationship where an entity is in conflict with, resists, or acts against a deity.
-
E.
notWorshippedAs
Indicates that one entity is not regarded, treated, or honored as an object of worship by another entity or group.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906ad50481909a700664e0b70fb0 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.