Triple
T24134992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breslov Hasidism |
E598057
|
entity |
| Predicate | pilgrimageOccasion |
P16196
|
FINISHED |
| Object | Rosh Hashanah |
—
|
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: Rosh Hashanah | Statement: [Breslov Hasidism, pilgrimageOccasion, Rosh Hashanah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageOccasion Context triple: [Breslov Hasidism, pilgrimageOccasion, Rosh Hashanah]
-
A.
majorPilgrimageEvent
Indicates a significant religious journey or gathering undertaken by many participants as a central act of devotion or worship.
-
B.
pilgrimageDate
Indicates the date on which a pilgrimage takes place or is scheduled to occur.
-
C.
pilgrimageAssociatedWith
chosen
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
D.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
-
E.
pilgrimagePractice
Indicates that an entity engages in, prescribes, or is associated with the religious act of undertaking a pilgrimage as a spiritual practice.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7b6e9c819097fb546efa35821b |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:26 p.m.