Triple
T3725054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yod |
E81727
|
entity |
| Predicate | usedInKabbalahSymbolism |
P51244
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yod, usedInKabbalahSymbolism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInKabbalahSymbolism Context triple: [Yod, usedInKabbalahSymbolism, true]
-
A.
associatedWithSephirahInSomeKabbalisticSystems
Indicates that something is linked or connected to a particular Sephirah within at least one interpretation or variant of Kabbalistic systems.
-
B.
usedInReligiousTextsOf
Indicates that something (such as a concept, term, or symbol) appears within and is employed in the religious texts associated with a particular religion or tradition.
-
C.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
D.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
usedInCulture
Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
- F. None of above. chosen
Provenance (4 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf54af881908bd8d520595de061 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.