Triple
T5784382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Univision |
E128232
|
entity |
| Predicate | typeOfBroadcast |
P9324
|
FINISHED |
| Object | commercial television |
—
|
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: commercial television | Statement: [Univision, typeOfBroadcast, commercial television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBroadcast Context triple: [Univision, typeOfBroadcast, commercial television]
-
A.
broadcasterType
chosen
Indicates the category or kind of broadcaster involved in the relationship or action (e.g., public, commercial, online).
-
B.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
C.
broadcastsContentType
Indicates that an entity (such as a broadcaster or channel) transmits or distributes content of a specified type.
-
D.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
-
E.
broadcastsTo
Indicates that one entity transmits or disseminates information, signals, or content to another entity or group of entities.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a19870c819084dc68b36b0cdd60 |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.