Triple
T26644588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jahmiyya |
E668869
|
entity |
| Predicate | doctrinalOpposite |
P50143
|
FINISHED |
| Object | Qadariyya |
—
|
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: Qadariyya | Statement: [Jahmiyya, doctrinalOpposite, Qadariyya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrinalOpposite Context triple: [Jahmiyya, doctrinalOpposite, Qadariyya]
-
A.
doctrinalOppositionFrom
chosen
Indicates a relationship where one party holds or expresses doctrinal disagreement or opposition toward another party or their teachings.
-
B.
doctrinalStance
Indicates the specific set of doctrines, beliefs, or official teachings that an entity adheres to or promotes.
-
C.
doctrinalTerm
Indicates that one entity is a doctrinal or theological term that conceptually characterizes, labels, or defines the other entity within a religious or ideological system.
-
D.
doctrinalStatus
Indicates the formal standing or classification of a belief, teaching, or doctrine within a particular religious or ideological system.
-
E.
doctrinalDomain
Indicates the specific area of doctrine or body of teachings within which a belief, statement, or rule is classified.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 2:30 a.m.