Triple
T25886883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox Tuesday comedy block |
E652213
|
entity |
| Predicate | timeSlotCategory |
P52643
|
FINISHED |
| Object | prime 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: prime time | Statement: [Fox Tuesday comedy block, timeSlotCategory, prime time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSlotCategory Context triple: [Fox Tuesday comedy block, timeSlotCategory, prime time]
-
A.
timeSlotOfWorks
Indicates the specific time period or interval during which the works (e.g., tasks, events, or activities) are scheduled or take place.
-
B.
timePeriodCategory
chosen
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
-
C.
calendarCategory
Indicates the classification or grouping assigned to calendar entries based on their type, purpose, or context.
-
D.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
E.
timeDesignation
Indicates that one entity assigns, specifies, or denotes a particular time or temporal label for another entity or event.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6034386208190a54585ce1e3ef5d1 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:18 a.m.