Triple
T24285723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midori no Hi |
E605663
|
entity |
| Predicate | predecessorHolidayOnApril29 |
P71491
|
FINISHED |
| Object | Shōwa Day |
—
|
NE NERFINISHED |
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: Shōwa Day | Statement: [Midori no Hi, predecessorHolidayOnApril29, Shōwa Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorHolidayOnApril29 Context triple: [Midori no Hi, predecessorHolidayOnApril29, Shōwa Day]
-
A.
predecessorHoliday
Indicates that one holiday directly precedes another in a temporal or calendrical sequence.
-
B.
replacedHolidayOnApril29
chosen
Indicates that one holiday has been substituted for or taken the place of another specifically on April 29.
-
C.
successorHolidayDate
Indicates that one holiday’s date directly follows or succeeds another holiday’s date in a temporal sequence.
-
D.
wasPublicHolidayUntil
Indicates that a given day or date range held the status of a public holiday up to, but not necessarily after, a specified end time or date.
-
E.
successorHolidayEnglishName
Indicates that one holiday is followed by another holiday, specifying the English name of the subsequent holiday in the sequence.
- 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.