Triple
T18170352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daytime Emmy Award for Outstanding Service Show |
E435007
|
entity |
| Predicate | broadcastTimeFocus |
P45316
|
FINISHED |
| Object | daytime |
—
|
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: daytime | Statement: [Daytime Emmy Award for Outstanding Service Show, broadcastTimeFocus, daytime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastTimeFocus Context triple: [Daytime Emmy Award for Outstanding Service Show, broadcastTimeFocus, daytime]
-
A.
broadcastTimeSlot
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
B.
broadcastDuring
chosen
Indicates that one event or program is broadcast while another specified time period or event is occurring.
-
C.
broadcastRuntime
Indicates that an entity transmits or distributes content or data during its execution period or operational timeframe.
-
D.
broadcastBegan
Indicates that the transmission or airing of a broadcast has started.
-
E.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df555af081908a2f12bce6a13f56 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.