Triple
T4877952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yetzirah |
E109249
|
entity |
| Predicate | associatedWithSoulLevel |
P11700
|
FINISHED |
| Object | Ruach |
—
|
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: Ruach | Statement: [Yetzirah, associatedWithSoulLevel, Ruach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSoulLevel Context triple: [Yetzirah, associatedWithSoulLevel, Ruach]
-
A.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
B.
associatedSpirit
Indicates a relationship where one entity is linked to or accompanied by a particular spirit, often as a guide, protector, or defining supernatural presence.
-
C.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
-
D.
associatedWithRank
chosen
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
E.
associatedWithPriceLevel
Indicates a relationship where something is linked or connected to a particular price level or pricing tier.
- 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.