Triple
T17052353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dominion Day |
E413729
|
entity |
| Predicate | publicHolidaySector |
P125669
|
FINISHED |
| Object | government offices closed |
—
|
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: government offices closed | Statement: [Dominion Day, publicHolidaySector, government offices closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicHolidaySector Context triple: [Dominion Day, publicHolidaySector, government offices closed]
-
A.
publicHolidayScope
Indicates the jurisdictional or contextual scope within which a public holiday is officially recognized or applicable.
-
B.
nationalHoliday
Indicates that a particular day is officially recognized and observed as a national holiday by a country or nation.
-
C.
nationalHolidayCountry
Indicates that a specific day is officially recognized as a national holiday in a given country.
-
D.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
E.
holidaySchedule
Indicates the planned dates, times, and durations during which holidays occur or are observed.
- F. None of above. chosen
Provenance (4 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa3324881908d9e445ba1cfe109 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.