Triple
T4877946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yetzirah |
E109249
|
entity |
| Predicate | associatedSefirahType |
P44934
|
FINISHED |
| Object | emotional sefirot |
—
|
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: emotional sefirot | Statement: [Yetzirah, associatedSefirahType, emotional sefirot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSefirahType Context triple: [Yetzirah, associatedSefirahType, emotional sefirot]
-
A.
associatedWithSephirahInSomeKabbalisticSystems
chosen
Indicates that something is linked or connected to a particular Sephirah within at least one interpretation or variant of Kabbalistic systems.
-
B.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
D.
associatedTarotPathInSomeSystems
Indicates that, in certain interpretive or esoteric systems, one entity is linked or mapped to a particular path within the Tarot framework.
-
E.
associatedCult
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.