Triple
T34556673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dashain |
E887222
|
entity |
| Predicate | governmentClosure |
P203221
|
FINISHED |
| Object | most 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: most government offices closed | Statement: [Dashain, governmentClosure, most government offices closed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentClosure Context triple: [Dashain, governmentClosure, most government offices closed]
-
A.
sectorClosures
Indicates that specific sectors or areas are closed, restricted, or otherwise unavailable for use or access.
-
B.
municipalOfficesOpened
Indicates that municipal government offices have begun operating or have been officially opened for public service.
-
C.
closedCityDuring
Indicates that a city is not accessible or operational during a specified time period or interval.
-
D.
schoolClosures
Indicates that schools are temporarily or permanently shut down, suspending normal in-person educational activities.
-
E.
closureDateForRegularService
Indicates the date on which a regular, ongoing service is formally closed or terminated.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_6a013d70e2448190a034e8a11a457008 |
completed | May 11, 2026, 2:22 a.m. |
Created at: May 1, 2026, 2:02 a.m.