Triple
T530191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sivan |
E12204
|
entity |
| Predicate | liturgicalSignificance |
P13038
|
FINISHED |
| Object | Time of receiving the Torah |
—
|
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: Time of receiving the Torah | Statement: [Sivan, liturgicalSignificance, Time of receiving the Torah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalSignificance Context triple: [Sivan, liturgicalSignificance, Time of receiving the Torah]
-
A.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
B.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
C.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
D.
liturgicalCharacter
chosen
Indicates the specific role, function, or significance that something holds within a liturgical or worship context.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- 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.