Triple
T6422262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Chodesh |
E127971
|
entity |
| Predicate | twoDayPattern |
P20585
|
FINISHED |
| Object | End of previous month and first day of new month |
—
|
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: End of previous month and first day of new month | Statement: [Rosh Chodesh, twoDayPattern, End of previous month and first day of new month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twoDayPattern Context triple: [Rosh Chodesh, twoDayPattern, End of previous month and first day of new month]
-
A.
dayPattern
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
B.
secondDayName
Indicates that one entity is the name or label assigned to the second day in a sequence of days associated with another entity.
-
C.
weekdayServicePattern
Indicates a service pattern or schedule that specifically applies on weekdays rather than weekends or holidays.
-
D.
repetitionPattern
Indicates a recurring structure or sequence in which an action, event, or element is repeated over time or across instances.
-
E.
observancePattern
chosen
Indicates how an action, rule, or practice is regularly carried out or followed over time, such as its schedule, frequency, or customary pattern of observance.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690576c48190b5db5464eacc9de3 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.