Triple
T13836471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ne’ilah |
E332541
|
entity |
| Predicate | fastingStatusOfParticipants |
P111698
|
FINISHED |
| Object | participants are fasting |
—
|
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: participants are fasting | Statement: [Ne’ilah, fastingStatusOfParticipants, participants are fasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastingStatusOfParticipants Context triple: [Ne’ilah, fastingStatusOfParticipants, participants are fasting]
-
A.
fastingDuration
Indicates the length of time that an entity abstains from eating (and possibly drinking), typically as part of a fasting practice.
-
B.
fastingIncludes
Indicates that a period of fasting encompasses or contains a specified component, practice, or time interval as part of that fast.
-
C.
includeFastingDays
Indicates whether a given schedule, plan, or regimen incorporates designated days of fasting as part of its structure or rules.
-
D.
hasFastingRule
Indicates that there is a prescribed rule or requirement regarding fasting that applies to the subject.
-
E.
typeOfFasting
Indicates the specific kind or category of fasting practice associated with an entity.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de029b352081909605baaedc336213 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:13 p.m.