Triple
T1066645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sons of Korah |
E23224
|
entity |
| Predicate | themeOfPsalms |
P13857
|
FINISHED |
| Object | trust in God amid distress |
—
|
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: trust in God amid distress | Statement: [Sons of Korah, themeOfPsalms, trust in God amid distress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeOfPsalms Context triple: [Sons of Korah, themeOfPsalms, trust in God amid distress]
-
A.
scripturalTheme
chosen
Indicates that one entity represents a central religious or theological theme expressed, discussed, or emphasized within a scriptural text or passage.
-
B.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
C.
themeInRabbinicLiterature
Indicates that a particular theme, concept, or motif is discussed, developed, or treated within rabbinic literature.
-
D.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
E.
importantHymn
Indicates that a hymn holds significant importance or prominence within a particular religious, cultural, or musical context.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.