Triple
T31708867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קבר רשב"י |
E809260
|
entity |
| Predicate | peakPilgrimageDay |
P134281
|
FINISHED |
| Object | ל"ג בעומר |
—
|
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: ל"ג בעומר | Statement: [קבר רשב"י, peakPilgrimageDay, ל"ג בעומר]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPilgrimageDay Context triple: [קבר רשב"י, peakPilgrimageDay, ל"ג בעומר]
-
A.
peakPilgrimageDays
Indicates the days during which pilgrimage activity reaches its highest intensity or volume.
-
B.
pilgrimagePeakDates
chosen
Indicates the specific dates during which a pilgrimage to a particular peak or sacred site customarily takes place.
-
C.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
D.
hasPilgrimagePeak
Indicates that a place or route is associated with a specific peak that serves as a destination or focal point for religious or spiritual pilgrimage.
-
E.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:14 p.m.