Triple
T18114704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Holiday Calendar |
E433574
|
entity |
| Predicate | hasAdventCalendar |
P130502
|
FINISHED |
| Object | magical antique advent calendar |
—
|
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: magical antique advent calendar | Statement: [The Holiday Calendar, hasAdventCalendar, magical antique advent calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdventCalendar Context triple: [The Holiday Calendar, hasAdventCalendar, magical antique advent calendar]
-
A.
hasSeasonalDecorations
Indicates that an entity is adorned with decorations that are specific to a particular season or holiday period.
-
B.
hasOccasionType
Indicates that an occasion, event, or happening is classified as being of a particular type or category.
-
C.
hasPreFestivePeriod
Indicates that an entity is associated with or occurs during a time period leading up to a specific festival or celebration.
-
D.
hasChristmasMarket
Indicates that a place or entity hosts or features a Christmas market.
-
E.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
- F. None of above. chosen
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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd4c7888190b85c39decdb0333f |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.