Triple
T8267499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pat Sajak Show |
E193336
|
entity |
| Predicate | followedByInTimeSlot |
P57693
|
FINISHED |
| Object | CBS Late Night programming blocks |
—
|
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: CBS Late Night programming blocks | Statement: [The Pat Sajak Show, followedByInTimeSlot, CBS Late Night programming blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByInTimeSlot Context triple: [The Pat Sajak Show, followedByInTimeSlot, CBS Late Night programming blocks]
-
A.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
-
B.
followsBetween
chosen
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
C.
followsTime
Indicates that one event, state, or time period occurs after and in temporal succession to another.
-
D.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
E.
followedByPeriod
Indicates that one event, state, or item is immediately succeeded in time or sequence by a subsequent period.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794fc4208190b268bc69ff2b28a9 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:50 p.m.