Triple
T529857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shalom Aleichem |
E12198
|
entity |
| Predicate | hasLiturgicalStatus |
P3655
|
FINISHED |
| Object | non-obligatory custom |
—
|
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: non-obligatory custom | Statement: [Shalom Aleichem, hasLiturgicalStatus, non-obligatory custom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalStatus Context triple: [Shalom Aleichem, hasLiturgicalStatus, non-obligatory custom]
-
A.
hasLiturgicalRank
chosen
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
hasPrimaryLiturgicalForm
Indicates that an entity is associated with its main or officially recognized liturgical form used in worship or religious practice.
-
C.
hasLiturgicalName
Indicates that an entity is associated with a specific name used in liturgical or religious worship contexts.
-
D.
hasLiturgicalCycle
Indicates that one entity follows, observes, or is structured according to a particular liturgical cycle associated with another entity.
-
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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.