Triple
T37536731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krampuslauf |
E933218
|
entity |
| Predicate | relatedToHoliday |
P39851
|
FINISHED |
| Object | Saint Nicholas Day |
E7602
|
NE 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: Saint Nicholas Day | Statement: [Krampuslauf, relatedToHoliday, Saint Nicholas Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToHoliday Context triple: [Krampuslauf, relatedToHoliday, Saint Nicholas Day]
-
A.
relatedHoliday
Indicates that there is an association or connection between two holidays, such as thematic, temporal, cultural, or contextual relatedness.
-
B.
hasHolidayAssociation
chosen
Indicates a relationship where something is connected or related to a holiday, such as by theme, usage, or occurrence.
-
C.
nationalHolidayConnection
Indicates a relationship where a date, event, or observance is officially recognized as a national holiday for a particular country or region.
-
D.
mentionsHoliday
Indicates that one entity refers to or brings up a holiday in relation to another entity or context.
-
E.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
- F. None of above.
Provenance (4 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40954c305c81908d733af56ed92ee0 |
completed | June 28, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.