Triple
T20430373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayyei ha-Olam ha-Ba |
E501112
|
entity |
| Predicate | viewsAfterlifeAs |
P11074
|
FINISHED |
| Object | state of spiritual closeness to God |
—
|
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: state of spiritual closeness to God | Statement: [Hayyei ha-Olam ha-Ba, viewsAfterlifeAs, state of spiritual closeness to God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsAfterlifeAs Context triple: [Hayyei ha-Olam ha-Ba, viewsAfterlifeAs, state of spiritual closeness to God]
-
A.
hasViewOnAfterlife
chosen
Indicates that an entity holds a particular belief, opinion, or perspective regarding the nature of the afterlife.
-
B.
viewOnLife
Indicates a person's general attitude, perspective, or philosophy regarding life.
-
C.
associatedAfterlife
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
D.
afterlife
Indicates a relationship where an entity exists or experiences a state following physical death or the end of mortal life.
-
E.
viewOfDeath
Indicates a subject’s beliefs, attitudes, or conceptual understanding regarding death.
- 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67bad58448190be1563d74dbf9957 |
completed | April 20, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.