Triple
T29975206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | けんこくきねんのひ |
E761423
|
entity |
| Predicate | 休日の種類 |
P2155
|
FINISHED |
| Object | 法定休日 |
—
|
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: 法定休日 | Statement: [けんこくきねんのひ, 休日の種類, 法定休日]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 休日の種類 Context triple: [けんこくきねんのひ, 休日の種類, 法定休日]
-
A.
holidayType
chosen
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
B.
dayType
Indicates the classification or category of a given day based on its characteristics or role (e.g., weekday, weekend, holiday).
-
C.
dayTypeVariation
Indicates a relationship where the type or classification of a day differs from a standard or reference day type (e.g., special, holiday, or exceptional schedule).
-
D.
primaryHoliday
Indicates that one holiday is the main or most significant holiday associated with a given entity, time, or context.
-
E.
holidayRole
Indicates the specific function, duty, or part an entity plays in relation to a holiday or holiday-related event.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678d44b848190a0c7887baf01b905 |
completed | May 2, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:33 p.m.