Triple
T16626468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Late Late Show with Tom Snyder |
E403957
|
entity |
| Predicate | targetTimeSlot |
P14564
|
FINISHED |
| Object | late night |
—
|
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: late night | Statement: [The Late Late Show with Tom Snyder, targetTimeSlot, late night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetTimeSlot Context triple: [The Late Late Show with Tom Snyder, targetTimeSlot, late night]
-
A.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
B.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
C.
scheduledDestinationAtTimeOfEvent
Indicates that an entity was planned or expected to be at a specific destination at the time a particular event occurred.
-
D.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
E.
broadcastTimeSlot
chosen
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375530ed081908337dc5c6360d733 |
completed | April 18, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.