Triple
T13787700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTVT |
E331306
|
entity |
| Predicate | digitalSubchannelContent |
P43291
|
FINISHED |
| Object | Fox network programming on 13.1 |
—
|
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: Fox network programming on 13.1 | Statement: [WTVT, digitalSubchannelContent, Fox network programming on 13.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalSubchannelContent Context triple: [WTVT, digitalSubchannelContent, Fox network programming on 13.1]
-
A.
digitalSubchannel
Indicates that one channel functions as a digital subchannel or subsidiary stream of another primary broadcast channel.
-
B.
hasDigitalSubchannels
Indicates that a broadcasting entity provides one or more additional digital subchannels alongside its primary digital channel.
-
C.
digitalProvider
Indicates that one entity serves as the supplier or source of digital services, content, or infrastructure for another entity.
-
D.
hdChannel
Indicates that a media service or content stream is provided in high-definition (HD) format.
-
E.
secondaryContentType
chosen
Indicates the type or category of additional, non-primary content associated with an entity or resource.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0249e4f88190a80316394940627d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.