Triple
T9912903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Believe… In Holiday Magic fireworks |
E185789
|
entity |
| Predicate | hasSeasonalSchedule |
P15928
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Believe… In Holiday Magic fireworks, hasSeasonalSchedule, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalSchedule Context triple: [Believe… In Holiday Magic fireworks, hasSeasonalSchedule, true]
-
A.
hasSeasonalPattern
Indicates that the occurrence, intensity, or characteristics of something regularly vary according to a recurring seasonal cycle.
-
B.
hasSeasonalStructure
Indicates that something exhibits a recurring pattern, organization, or behavior that varies systematically with the seasons.
-
C.
hasSeasonalStatus
chosen
Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
-
D.
hasSeasonFrequency
Indicates how often something occurs or is scheduled within a specific season.
-
E.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb53a300481909d917e487d8aab56 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.