Triple
T24285635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gōruden Wīku |
E605661
|
entity |
| Predicate | holidaySystem |
P84013
|
FINISHED |
| Object | Japanese public holidays law |
—
|
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: Japanese public holidays law | Statement: [Gōruden Wīku, holidaySystem, Japanese public holidays law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holidaySystem Context triple: [Gōruden Wīku, holidaySystem, Japanese public holidays law]
-
A.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
B.
holidayRole
Indicates the specific function, duty, or part an entity plays in relation to a holiday or holiday-related event.
-
C.
holidaySchedule
Indicates the planned dates, times, and durations during which holidays occur or are observed.
-
D.
holidayAssociation
Indicates a relationship where one entity is connected to, themed around, or designated for a particular holiday.
-
E.
holidayDateSystem
chosen
Indicates the system or convention used to determine and represent the date on which a holiday occurs.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5605f081908367bd08ab1ec9ab |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.