Triple
T19541406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Israel of Great Neck |
E488911
|
entity |
| Predicate | offersReligiousServices |
P77850
|
FINISHED |
| Object | Shabbat services |
—
|
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: Shabbat services | Statement: [Young Israel of Great Neck, offersReligiousServices, Shabbat services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersReligiousServices Context triple: [Young Israel of Great Neck, offersReligiousServices, Shabbat services]
-
A.
hasWorshipServices
chosen
Indicates that an entity conducts or provides organized religious worship services.
-
B.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
C.
offersMinistry
Indicates that one entity provides or makes available a ministry or ministerial service to another entity.
-
D.
religiousActivity
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
E.
liturgicalServices
Indicates that one entity conducts, provides, or is associated with formal acts of public worship or religious rites for another entity 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63872fda48190bbb1f465cb7b57fe |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.