Triple
T25356820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jingle Bell Rock |
E635843
|
entity |
| Predicate | hasBroadcastCategory |
P160917
|
FINISHED |
| Object | holiday music rotation |
—
|
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: holiday music rotation | Statement: [Jingle Bell Rock, hasBroadcastCategory, holiday music rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastCategory Context triple: [Jingle Bell Rock, hasBroadcastCategory, holiday music rotation]
-
A.
hasBroadcastStatus
Indicates the current broadcast-related state or condition of an item, such as whether it is scheduled, live, completed, or unavailable.
-
B.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
C.
hasBroadcastContent
Indicates that one entity (typically a broadcast or channel) carries, includes, or transmits the specified content.
-
D.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
E.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 21, 2026, 1:36 p.m.