Triple
T24857527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph |
E622066
|
entity |
| Predicate | symbolismInKabbalah |
P51244
|
FINISHED |
| Object | unity of the divine |
—
|
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: unity of the divine | Statement: [Aleph, symbolismInKabbalah, unity of the divine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolismInKabbalah Context triple: [Aleph, symbolismInKabbalah, unity of the divine]
-
A.
usedInKabbalahSymbolism
chosen
Indicates that something is employed as a symbol or motif within the mystical concepts, practices, or interpretive frameworks of Kabbalah.
-
B.
symbolInJewishTradition
Indicates that something functions as a recognized symbol within Jewish religious, cultural, or historical tradition.
-
C.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
D.
languageOfSymbolism
Indicates that one entity is the language in which the symbolic meaning or symbolism of another entity is expressed or encoded.
-
E.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.