Triple
T5184345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Or ha-Sekhel |
E116994
|
entity |
| Predicate | mysticalOrientation |
P49306
|
FINISHED |
| Object | Ecstatic mysticism |
—
|
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: Ecstatic mysticism | Statement: [Or ha-Sekhel, mysticalOrientation, Ecstatic mysticism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mysticalOrientation Context triple: [Or ha-Sekhel, mysticalOrientation, Ecstatic mysticism]
-
A.
spiritualityType
chosen
Indicates the specific kind or category of spirituality associated with an entity.
-
B.
spiritualQuest
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
-
C.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
D.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
E.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799eb90c8190b738e9478699180f |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.