Triple
T26998019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icelandic National Day |
E680027
|
entity |
| Predicate | hasPublicHolidayStatus |
P38041
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Icelandic National Day, hasPublicHolidayStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicHolidayStatus Context triple: [Icelandic National Day, hasPublicHolidayStatus, yes]
-
A.
hasOfficialHoliday
chosen
Indicates that a particular date, event, or period is formally recognized as an official holiday by an authority or governing body.
-
B.
hasPublicHolidayOrFestival
Indicates that there exists a public holiday or festival associated with, occurring in, or relevant to the given entity.
-
C.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
D.
hasHolidayAssociation
Indicates a relationship where something is connected or related to a holiday, such as by theme, usage, or occurrence.
-
E.
haveOwnPublicHolidays
Indicates that an entity possesses its own distinct set of officially recognized public holidays, separate from those of other entities.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 6:55 a.m.