Triple
T23392472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitnagdim |
E594054
|
entity |
| Predicate | accusedHasidimOf |
P14607
|
FINISHED |
| Object | deviating from traditional Jewish practice |
—
|
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: deviating from traditional Jewish practice | Statement: [Mitnagdim, accusedHasidimOf, deviating from traditional Jewish practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedHasidimOf Context triple: [Mitnagdim, accusedHasidimOf, deviating from traditional Jewish practice]
-
A.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
B.
accusedGroup
chosen
Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
-
C.
numberOfJewsArrested
Indicates the quantity of Jewish individuals who were apprehended or taken into custody in a given event or context.
-
D.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
E.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49df4308190ab4ab31310af81ed |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.