Triple
T6422413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaddish |
E127974
|
entity |
| Predicate | mourningPractice |
P59695
|
FINISHED |
| Object | recited for deceased relatives |
—
|
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: recited for deceased relatives | Statement: [Kaddish, mourningPractice, recited for deceased relatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mourningPractice Context triple: [Kaddish, mourningPractice, recited for deceased relatives]
-
A.
mourningCustom
chosen
Indicates a culturally prescribed way in which people are expected to express grief and honor the dead after a loss.
-
B.
mourningEmphasizedBy
Indicates that one instance of mourning is made more intense, prominent, or noticeable due to the influence or presence of another factor or expression.
-
C.
mourningLevel
Indicates the degree or intensity to which an entity is experiencing or expressing mourning in response to a loss.
-
D.
mourningPeriodBegins
Indicates that the formal period of mourning for a death or loss has started.
-
E.
mourningIntensifiesIn
Indicates that the level or expression of mourning becomes stronger or more intense within a specified context, period, or situation.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690576c48190b5db5464eacc9de3 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.