Triple
T651554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lecha Dodi |
E11354
|
entity |
| Predicate | statusInLiturgy |
P9871
|
FINISHED |
| Object | widely accepted standard part of Kabbalat Shabbat |
—
|
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: widely accepted standard part of Kabbalat Shabbat | Statement: [Lecha Dodi, statusInLiturgy, widely accepted standard part of Kabbalat Shabbat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInLiturgy Context triple: [Lecha Dodi, statusInLiturgy, widely accepted standard part of Kabbalat Shabbat]
-
A.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
B.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
C.
usedInLiturgy
chosen
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
D.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
E.
liturgicalUseApprovedBy
Indicates that the use of a liturgical text, rite, or practice has been formally authorized or approved by a specified authority.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f35acb08190a3a8248023ce07f9 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.