Triple
T3143758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Today (U.S. TV program) |
E65713
|
entity |
| Predicate | expandedTimeSlot |
P14564
|
FINISHED |
| Object | 7:00–11:00 a.m. Eastern Time |
—
|
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: 7:00–11:00 a.m. Eastern Time | Statement: [Today (U.S. TV program), expandedTimeSlot, 7:00–11:00 a.m. Eastern Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedTimeSlot Context triple: [Today (U.S. TV program), expandedTimeSlot, 7:00–11:00 a.m. Eastern Time]
-
A.
expandedDuring
Indicates that an entity increased in size, scope, or extent over the course of a specified time period or event.
-
B.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
-
C.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59489a88190b0962cef091f4ddb |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.