Triple
T9794530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Enough at Last |
E237685
|
entity |
| Predicate | firstBroadcastSlot |
P54498
|
FINISHED |
| Object | Friday 10:00 PM ET |
—
|
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: Friday 10:00 PM ET | Statement: [Time Enough at Last, firstBroadcastSlot, Friday 10:00 PM ET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBroadcastSlot Context triple: [Time Enough at Last, firstBroadcastSlot, Friday 10:00 PM ET]
-
A.
firstBroadcastTime
chosen
Indicates the date and time at which something (typically a program or content) was first broadcast.
-
B.
firstBroadcast
Indicates the date or event of the initial public transmission or airing of a program, signal, or content.
-
C.
firstBroadcastBy
Indicates that one entity is the original broadcaster or channel that first aired the other entity (such as a program, event, or content).
-
D.
firstBroadcastOrder
Indicates the sequence position in which something was originally broadcast relative to other broadcasts.
-
E.
firstBroadcastAsPartOf
Indicates that an entity’s first broadcast occurred as a component or segment within a larger program, series, or event rather than as a standalone broadcast.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda347b6bc8190a99b7dec1650cd46 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.