Triple
T3278321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seventeenth of Tammuz |
E68810
|
entity |
| Predicate | prayerChanges |
P16687
|
FINISHED |
| Object | Aneinu added in Amidah in many communities |
—
|
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: Aneinu added in Amidah in many communities | Statement: [Seventeenth of Tammuz, prayerChanges, Aneinu added in Amidah in many communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayerChanges Context triple: [Seventeenth of Tammuz, prayerChanges, Aneinu added in Amidah in many communities]
-
A.
associatedPrayerChange
chosen
Indicates a change in a prayer that is linked or connected to another entity, event, or condition.
-
B.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
C.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
D.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
E.
isAddressedInPrayer
Indicates that an entity is the recipient or target of a prayer being spoken or offered.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb013de048190bcaac732caa6b174 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.