Triple
T21029433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kether |
E518025
|
entity |
| Predicate | qabalisticWorldFunction |
P20395
|
FINISHED |
| Object | source of all subsequent sephiroth |
—
|
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: source of all subsequent sephiroth | Statement: [Kether, qabalisticWorldFunction, source of all subsequent sephiroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qabalisticWorldFunction Context triple: [Kether, qabalisticWorldFunction, source of all subsequent sephiroth]
-
A.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
B.
cosmicFunction
chosen
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
C.
functionInBeliefSystem
Indicates that one entity serves a particular role, purpose, or function within the structure or doctrine of a belief system.
-
D.
hasWorldSoul
Indicates that an entity possesses or is intrinsically connected to a fundamental, unifying spiritual essence of a world or cosmos.
-
E.
hasNumberOfSephirot
Indicates the specific count of sephirot associated with or attributed to an entity.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7fd3ec81908ac237047f9b0d7a |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.