Triple
T5333179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WGN Radio |
E123359
|
entity |
| Predicate | programContent |
P62881
|
FINISHED |
| Object | local news coverage of Chicago and suburbs |
—
|
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: local news coverage of Chicago and suburbs | Statement: [WGN Radio, programContent, local news coverage of Chicago and suburbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programContent Context triple: [WGN Radio, programContent, local news coverage of Chicago and suburbs]
-
A.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
B.
programDocument
Indicates that a document is associated with, defines, or describes a particular program (such as a software application, project, or initiative).
-
C.
programStructure
Indicates how components, modules, or elements are organized and related within a program or system.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
programIncluded
Indicates that a particular program is contained within, or forms part of, another specified collection, package, or set of programs.
- F. None of above. chosen
Provenance (4 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ac8e10819088b6a9e02d927044 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.