Triple
T9827699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag Day (May 2) |
E238698
|
entity |
| Predicate | workHolidayStatus |
P17615
|
FINISHED |
| Object | not a public non-working holiday |
—
|
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: not a public non-working holiday | Statement: [Flag Day (May 2), workHolidayStatus, not a public non-working holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workHolidayStatus Context triple: [Flag Day (May 2), workHolidayStatus, not a public non-working holiday]
-
A.
holidayStatus
chosen
Indicates the current holiday-related state or condition associated with an entity, such as whether it is a holiday, non-holiday, or a specific holiday type.
-
B.
isWorkHoliday
Indicates that a given day is designated as a non-working public or company holiday.
-
C.
publicHolidayStatusSince
Indicates that an entity’s public holiday status has been in effect starting from a specified point in time.
-
D.
holidaySchedule
Indicates the planned dates, times, and durations during which holidays occur or are observed.
-
E.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb324e7848190b9424a78ca653afe |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.