Triple
T33635631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Muslim Mission |
E861683
|
entity |
| Predicate | doctrinalShiftTo |
P56048
|
FINISHED |
| Object | mainstream Sunni doctrine |
—
|
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: mainstream Sunni doctrine | Statement: [American Muslim Mission, doctrinalShiftTo, mainstream Sunni doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrinalShiftTo Context triple: [American Muslim Mission, doctrinalShiftTo, mainstream Sunni doctrine]
-
A.
doctrinalChange
chosen
Indicates a modification or shift in an established set of principles, teachings, or doctrines within a belief or rule system.
-
B.
doctrinalDomain
Indicates the specific area of doctrine or body of teachings within which a belief, statement, or rule is classified.
-
C.
doctrinalTheme
Indicates that one entity concerns, expresses, or is characterized by a particular doctrinal or theological theme in relation to another.
-
D.
doctrinalInfluenceOn
Indicates that one doctrine has influenced, shaped, or contributed to the development of another doctrine.
-
E.
doctrinalStance
Indicates the specific set of doctrines, beliefs, or official teachings that an entity adheres to or promotes.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:42 a.m.