Triple
T1056305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL on TNT |
E22802
|
entity |
| Predicate | broadcastScheduleIncludes |
P18648
|
FINISHED |
| Object | Wednesday night NHL games |
—
|
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: Wednesday night NHL games | Statement: [NHL on TNT, broadcastScheduleIncludes, Wednesday night NHL games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastScheduleIncludes Context triple: [NHL on TNT, broadcastScheduleIncludes, Wednesday night NHL games]
-
A.
broadcastTimeSlot
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
B.
broadcastProgram
Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
-
C.
broadcastDay
Indicates the specific day on which a program, event, or content is broadcast or scheduled to be broadcast.
-
D.
showSchedule
chosen
Indicates that an entity presents or displays a timetable or planned sequence of events for another entity.
-
E.
usedForTelevisionBroadcastSchedules
Indicates that something is utilized to organize, present, or manage the timing and content of television broadcast schedules.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d9102c819090af78cae50f0ff2 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.