Triple
T23728263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igeret HaKodesh |
E586338
|
entity |
| Predicate | religiousSubdomain |
P47348
|
FINISHED |
| Object | Kabbalah |
—
|
NE NERFINISHED |
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: Kabbalah | Statement: [Igeret HaKodesh, religiousSubdomain, Kabbalah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousSubdomain Context triple: [Igeret HaKodesh, religiousSubdomain, Kabbalah]
-
A.
religiousTopicAddressed
chosen
Indicates that a subject deals with, discusses, or focuses on a religious theme, issue, or question.
-
B.
religiousEnvironment
Indicates the religious context, atmosphere, or setting in which an entity exists or an action takes place.
-
C.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
D.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
E.
religiousFoundation
Indicates that an entity was established, created, or founded by a religious organization, authority, or tradition.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91740ac81908ca99de0c56f6b57 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:09 p.m.