Triple
T24783814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogfather |
E620065
|
entity |
| Predicate | inUniverseHolidayType |
P39851
|
FINISHED |
| Object | winter festival |
—
|
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: winter festival | Statement: [Hogfather, inUniverseHolidayType, winter festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseHolidayType Context triple: [Hogfather, inUniverseHolidayType, winter festival]
-
A.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
B.
hasHolidayAssociation
chosen
Indicates a relationship where something is connected or related to a holiday, such as by theme, usage, or occurrence.
-
C.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
D.
hasHolidayCountry
Indicates that a specific holiday is officially observed or associated with a particular country.
-
E.
hasHolidayAnalog
Indicates that one entity has a corresponding or comparable counterpart in the context of a holiday or holiday-related tradition.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:45 a.m.