Triple
T25249910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run Run Rudolph |
E632709
|
entity |
| Predicate | typicalAirplayPeriod |
P185616
|
FINISHED |
| Object | Christmas season |
—
|
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: Christmas season | Statement: [Run Run Rudolph, typicalAirplayPeriod, Christmas season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAirplayPeriod Context triple: [Run Run Rudolph, typicalAirplayPeriod, Christmas season]
-
A.
hasNotableAirplayPeriod
chosen
Indicates that an entity experienced a distinct period during which it received significant or notable airplay.
-
B.
supportsAirPlay
Indicates that one entity is capable of sending or receiving media via Apple’s AirPlay streaming protocol in relation to another entity.
-
C.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
D.
hasNotableAirplay
Indicates that something (typically a song, program, or audio content) has received a significant amount of broadcast play on radio or similar media.
-
E.
typicalBroadcastPeriod
Indicates the usual or standard time interval during which something is broadcast or transmitted.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 21, 2026, 1:11 p.m.