Triple
T202174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yom Kippur |
E4528
|
entity |
| Predicate | fastingRequired |
P6166
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yom Kippur, fastingRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastingRequired Context triple: [Yom Kippur, fastingRequired, yes]
-
A.
preparatoryFastBegins
Indicates that a required period of fasting starts in preparation for a subsequent event, action, or ritual.
-
B.
isNotRequiredFor
Indicates that one entity is not necessary or mandatory for the existence, occurrence, validity, or completion of another entity or process.
-
C.
waterRequirement
Indicates the amount or conditions of water needed for an entity to grow, function, or be maintained properly.
-
D.
religiousRestriction
chosen
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.