Triple
T19860487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congregation Shaar Hashomayim |
E477241
|
entity |
| Predicate | hasReligiousCalendar |
P28460
|
FINISHED |
| Object | Jewish calendar |
—
|
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: Jewish calendar | Statement: [Congregation Shaar Hashomayim, hasReligiousCalendar, Jewish calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousCalendar Context triple: [Congregation Shaar Hashomayim, hasReligiousCalendar, Jewish calendar]
-
A.
religiousCalendar
chosen
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
-
B.
isReligiousCalendarMonthIn
Indicates that a specific month belongs to or occurs within a particular religious calendar system.
-
C.
hasReligiousObservance
Indicates that an entity practices, observes, or participates in a particular religious rite, ceremony, or tradition.
-
D.
hasRitualCalendar
Indicates that an entity maintains or is associated with a structured schedule of ritual or ceremonial events.
-
E.
religiousHolidayCelebrated
Indicates that a particular religious holiday is observed or celebrated by an entity.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589a68b081908c2f333b6a292a1f |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.