Triple
T11581175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DZBB-TV |
E274628
|
entity |
| Predicate | analogChannelBand |
P47328
|
FINISHED |
| Object | VHF |
—
|
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: VHF | Statement: [DZBB-TV, analogChannelBand, VHF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analogChannelBand Context triple: [DZBB-TV, analogChannelBand, VHF]
-
A.
analogChannel
Indicates a relationship where a channel carries or transmits signals in analog (continuously varying) form rather than digital form.
-
B.
formerAnalogChannel
Indicates that an entity was previously an analog channel but no longer holds that status.
-
C.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
D.
transmissionBand
chosen
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
E.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904c51b881909e7be84c6f3de79f |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.