Triple
T38037128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | בני ברק |
E949380
|
entity |
| Predicate | hasHasidicDynastyCenter |
P190236
|
FINISHED |
| Object | גור |
—
|
NE NERFINISHED |
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: גור | Statement: [בני ברק, hasHasidicDynastyCenter, גור]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHasidicDynastyCenter Context triple: [בני ברק, hasHasidicDynastyCenter, גור]
-
A.
notableHasidicDynastyOrigin
Indicates that a notable Hasidic dynasty traces its origin or founding to the specified place or context.
-
B.
hasJewishInstitution
Indicates that a place, organization, or entity possesses, hosts, or is associated with a Jewish religious, cultural, or educational institution.
-
C.
hasJewishDenomination
Indicates that an entity is associated with, or belongs to, a specific Jewish religious denomination or movement.
-
D.
viewOnHasidism
Indicates the stance, opinion, or perspective that one entity holds regarding Hasidism.
-
E.
hasSignificantJewishCommunity
Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
- F. None of above. chosen
Provenance (4 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:20 p.m.