Triple
T21029458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geburah |
E518026
|
entity |
| Predicate | positionRelativeToOtherSephirot |
P64247
|
FINISHED |
| Object | below Binah |
—
|
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: below Binah | Statement: [Geburah, positionRelativeToOtherSephirot, below Binah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToOtherSephirot Context triple: [Geburah, positionRelativeToOtherSephirot, below Binah]
-
A.
positionRelativeToGevurah
Indicates a spatial or conceptual placement of one entity in relation to the entity or aspect referred to as Gevurah.
-
B.
relationshipToOtherSefirot
chosen
Indicates how one sefirah is connected or related to other sefirot within the overall structure or network of sefirot.
-
C.
isPositionInSefirot
Indicates that one entity occupies a specific position or role within the structured hierarchy of the Sefirot.
-
D.
positionRelativeToChesed
Indicates the spatial or conceptual position of something in relation to Chesed.
-
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.