Triple
T4768711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ein Sof |
E105872
|
entity |
| Predicate | modeOfRelationToWorld |
P11529
|
FINISHED |
| Object | emanation through 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: emanation through Sefirot | Statement: [Ein Sof, modeOfRelationToWorld, emanation through Sefirot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfRelationToWorld Context triple: [Ein Sof, modeOfRelationToWorld, emanation through Sefirot]
-
A.
relationshipToWorld
chosen
Indicates how an entity is connected or related to the broader world or external environment.
-
B.
morphologicalRelation
Indicates a relationship between linguistic forms where one word or morpheme is derived from, inflected from, or otherwise morphologically related to another.
-
C.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
D.
spatialRelation
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
E.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.