Triple
T617570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheshvan |
E14439
|
entity |
| Predicate | containsFastDay |
P15537
|
FINISHED |
| Object | none of the four major public fasts |
—
|
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: none of the four major public fasts | Statement: [Cheshvan, containsFastDay, none of the four major public fasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFastDay Context triple: [Cheshvan, containsFastDay, none of the four major public fasts]
-
A.
hasDays
Indicates that an entity is associated with, spans, or occurs on specific days.
-
B.
majorFastDay
chosen
Indicates that an entity is associated with a significant religious fast day observed with major or stringent fasting practices.
-
C.
hasDayNumberRange
Indicates that something is associated with a contiguous range of day numbers between a specified minimum and maximum value.
-
D.
isFederalHoliday
Indicates that a given day is officially recognized as a federal holiday by the national government.
-
E.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.