Triple
T9593332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WVII-TV |
E231470
|
entity |
| Predicate | broadcastService |
P89980
|
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: [WVII-TV, broadcastService, commercial television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastService Context triple: [WVII-TV, broadcastService, commercial television]
-
A.
broadcastVia
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
B.
broadcastModel
Indicates that one entity serves as the template or source whose structure or values are replicated and applied across another entity or set of entities.
-
C.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
D.
broadcastDuring
Indicates that one event or program is broadcast while another specified time period or event is occurring.
-
E.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a134b0c81908a568e5d2ecfbb92 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:07 p.m.