Triple
T21579660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli national holidays |
E532490
|
entity |
| Predicate | typicalClosures |
P144337
|
FINISHED |
| Object | government offices |
—
|
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 | Statement: [Israeli national holidays, typicalClosures, government offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClosures Context triple: [Israeli national holidays, typicalClosures, government offices]
-
A.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
B.
typicalClosing
Indicates that an entity represents a standard or commonly used way of ending or concluding another entity (such as a message, document, or interaction).
-
C.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
D.
notableClosure
Indicates that an entity is recognized for a significant or noteworthy ending, shutdown, or termination event.
-
E.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5b8118819095fd751a03fbe8e8 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:31 p.m.