Triple
T23392476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitnagdim |
E594054
|
entity |
| Predicate | historicalRelationshipWithHasidim |
P71068
|
FINISHED |
| Object | initially hostile |
—
|
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: initially hostile | Statement: [Mitnagdim, historicalRelationshipWithHasidim, initially hostile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRelationshipWithHasidim Context triple: [Mitnagdim, historicalRelationshipWithHasidim, initially hostile]
-
A.
relationshipToJews
Indicates how an entity is related or connected to Jewish people, communities, or Judaism.
-
B.
hasJewishCommunityHistory
Indicates that there is a documented history of a Jewish community being present, active, or influential in relation to the subject.
-
C.
viewOnHasidism
chosen
Indicates the stance, opinion, or perspective that one entity holds regarding Hasidism.
-
D.
hasSynagogueHistory
Indicates that there exists a historical relationship or record connecting an entity to a synagogue, such as past ownership, use, events, or significance.
-
E.
notableHasidicDynastyOrigin
Indicates that a notable Hasidic dynasty traces its origin or founding to the specified place or 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_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.