Triple
T28660480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMUR-TV |
E725453
|
entity |
| Predicate | hasSubchannels |
P82648
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WMUR-TV, hasSubchannels, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubchannels Context triple: [WMUR-TV, hasSubchannels, yes]
-
A.
hasDigitalSubchannels
chosen
Indicates that a broadcasting entity provides one or more additional digital subchannels alongside its primary digital channel.
-
B.
hasSisterChannel
Indicates that one media channel is related to another as its sister channel, typically under common ownership or branding.
-
C.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
D.
hasSubSeries
Indicates that one series is a subordinate or component series within a larger parent series.
-
E.
hasSpecialtyChannel
Indicates that one entity provides or is associated with a dedicated channel focused on a particular specialty or subject area for another entity.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 28, 2026, 4:57 a.m.