Triple
T974373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinclair Broadcast Group |
E21016
|
entity |
| Predicate | hasBroadcastAssets |
P7587
|
FINISHED |
| Object | television stations in multiple U.S. markets |
—
|
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: television stations in multiple U.S. markets | Statement: [Sinclair Broadcast Group, hasBroadcastAssets, television stations in multiple U.S. markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastAssets Context triple: [Sinclair Broadcast Group, hasBroadcastAssets, television stations in multiple U.S. markets]
-
A.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
B.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
C.
hasAsset
chosen
Indicates that one entity possesses, owns, or controls another entity as an asset.
-
D.
hasBroadcastRightsHolder
Indicates that one entity holds the legal rights to broadcast content owned or controlled by another entity.
-
E.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b460a5c0819087b03dfb8a3af2c2 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.