Triple
T5839340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesychast controversy |
E129552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mystical dispute |
C3649
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: mystical dispute Context triple: [Hesychast controversy, instanceOf, mystical dispute]
-
A.
theological dispute
chosen
A theological dispute is a conflict or debate between individuals or groups over differing interpretations of religious doctrines, beliefs, or sacred texts.
-
B.
mystical system
A mystical system is a structured framework of beliefs, practices, and symbols designed to facilitate direct, often transcendent experiences of ultimate reality or hidden spiritual truths.
-
C.
mystic
A mystic is an individual who seeks direct, experiential communion with the divine or ultimate reality, often through contemplation, meditation, or esoteric practices beyond conventional religious doctrine.
-
D.
mystical concept
A mystical concept is an abstract idea or principle that relates to transcendent, spiritual, or esoteric aspects of reality, often beyond direct empirical understanding.
-
E.
mystical attribute
A mystical attribute is an inherent, often supernatural quality or property that imbues an entity, object, or phenomenon with enigmatic, otherworldly, or magical significance beyond ordinary understanding.
- F. None of above.
Provenance (1 batch)
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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:54 p.m.