Triple
T24746082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBS TV network |
E618701
|
entity |
| Predicate | broadcastsProgramType |
P15169
|
FINISHED |
| Object | breaking news coverage |
—
|
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: breaking news coverage | Statement: [IBS TV network, broadcastsProgramType, breaking news coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastsProgramType Context triple: [IBS TV network, broadcastsProgramType, breaking news coverage]
-
A.
broadcastProgram
Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
-
B.
broadcastsContentType
chosen
Indicates that an entity (such as a broadcaster or channel) transmits or distributes content of a specified type.
-
C.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
D.
targetAudienceOfPrograms
Indicates that a particular group or entity is the intended audience or recipient of certain programs.
-
E.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:21 a.m.