Triple
T20786005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remembrance Day (Dodenherdenking) |
E511638
|
entity |
| Predicate | relatedHolidayDate |
P361
|
FINISHED |
| Object | 5 May |
—
|
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: 5 May | Statement: [Remembrance Day (Dodenherdenking), relatedHolidayDate, 5 May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedHolidayDate Context triple: [Remembrance Day (Dodenherdenking), relatedHolidayDate, 5 May]
-
A.
relatedHoliday
Indicates that there is an association or connection between two holidays, such as thematic, temporal, cultural, or contextual relatedness.
-
B.
nationalHolidayDate
chosen
Indicates the specific calendar date on which a given national holiday is officially observed.
-
C.
holidayDateSystem
Indicates the system or convention used to determine and represent the date on which a holiday occurs.
-
D.
nationalHolidayBasedOn
Indicates that a national holiday is established, scheduled, or defined in relation to a particular event, date, person, or occasion.
-
E.
shareNationalHolidaysWith
Indicates that two entities observe the same set or a substantially overlapping set of national holidays.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28c0d0c8190aa48e6fdfdaab750 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.