Triple
T5534113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | January |
E145117
|
entity |
| Predicate | beginsOnDayOfWeekPattern |
P22124
|
FINISHED |
| Object | varies by year |
—
|
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: varies by year | Statement: [January, beginsOnDayOfWeekPattern, varies by year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beginsOnDayOfWeekPattern Context triple: [January, beginsOnDayOfWeekPattern, varies by year]
-
A.
startsOnDay
Indicates that an event or process begins on a specified calendar day.
-
B.
startDayOfWeek
chosen
Indicates the specific day of the week on which a given period, schedule, or recurring event begins.
-
C.
ifOnSundayObservedOn
Indicates that when an event or obligation falls on a Sunday, it is instead observed or carried out on a different specified day.
-
D.
weekdayServicePattern
Indicates a service pattern or schedule that specifically applies on weekdays rather than weekends or holidays.
-
E.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fa0141c81909a216be9f48d64e1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.