Triple
T113117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Hashanah |
E2287
|
entity |
| Predicate | prayerType |
P2154
|
FINISHED |
| Object | Amidah with special additions |
—
|
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: Amidah with special additions | Statement: [Rosh Hashanah, prayerType, Amidah with special additions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerType Context triple: [Rosh Hashanah, prayerType, Amidah with special additions]
-
A.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
B.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
C.
religiousElement
chosen
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
D.
religiousPhraseOptional
Indicates that a religious phrase may be present in the context but is not required.
-
E.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.