Triple
T14300482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakfast News |
E354547
|
entity |
| Predicate | hasBroadcastTimeOfDay |
P6019
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [Breakfast News, hasBroadcastTimeOfDay, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastTimeOfDay Context triple: [Breakfast News, hasBroadcastTimeOfDay, morning]
-
A.
hasBroadcastTime
Indicates that a broadcast (such as a program or transmission) is scheduled or occurs at a specific time.
-
B.
hasTimeOfDay
chosen
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
C.
broadcastDay
Indicates the specific day on which a program, event, or content is broadcast or scheduled to be broadcast.
-
D.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
E.
hasTimeIndication
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717e246c819083e67ac2b3b77881 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.