Triple
T5871131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WLS-TV |
E130516
|
entity |
| Predicate | transmissionPowerType |
P67317
|
FINISHED |
| Object | high-power UHF digital |
—
|
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: high-power UHF digital | Statement: [WLS-TV, transmissionPowerType, high-power UHF digital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionPowerType Context triple: [WLS-TV, transmissionPowerType, high-power UHF digital]
-
A.
transmissionType
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
B.
transmissionPattern
Indicates how something is passed or spread from one entity to another, such as the mode or route of transmission.
-
C.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
D.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
E.
transmissionFactor
Indicates how strongly or efficiently something is passed or transmitted from one entity to another.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0432f06fc8190bc047d52ffc30d59 |
completed | March 22, 2026, 7:29 p.m. |
Created at: March 22, 2026, 3:56 p.m.