Triple
T158717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabbalah |
E3232
|
entity |
| Predicate | viewOnSoul |
P6840
|
FINISHED |
| Object | soul having multiple levels |
—
|
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: soul having multiple levels | Statement: [Kabbalah, viewOnSoul, soul having multiple levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnSoul Context triple: [Kabbalah, viewOnSoul, soul having multiple levels]
-
A.
viewsGraceAs
Indicates that one entity regards or perceives Grace in a particular way or role.
-
B.
viewOnState
Indicates that one entity holds or expresses a particular opinion, stance, or perspective regarding a specific state or condition.
-
C.
viewOnChurchState
Indicates a stance or opinion an entity holds regarding the proper relationship between religious institutions and governmental authority.
-
D.
viewedByEasternTheologyAs
Indicates that something is regarded or interpreted in a particular way within the framework of Eastern Christian theological thought.
-
E.
hasSpiritualSource
Indicates that something originates from, is derived from, or is fundamentally grounded in a spiritual or non-material source.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.