Triple
T31626461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Jews |
E807037
|
entity |
| Predicate | typicalRite |
P23108
|
FINISHED |
| Object | Ashkenazi rite |
—
|
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: Ashkenazi rite | Statement: [Russian Jews, typicalRite, Ashkenazi rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRite Context triple: [Russian Jews, typicalRite, Ashkenazi rite]
-
A.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
B.
dominantRite
chosen
Indicates that one religious rite or liturgical tradition holds primary or prevailing status over others within a given context or community.
-
C.
observedInRite
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
D.
ritualChurch
Indicates a relationship where a ritual is formally associated with, performed within, or prescribed by a church or church institution.
-
E.
followsRitualTraditionOf
Indicates that one entity practices, observes, or adheres to the ritual traditions established or maintained by another entity.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:43 p.m.