Triple
T32029313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KUOW-FM |
E817905
|
entity |
| Predicate | hasDigitalBroadcast |
P111464
|
FINISHED |
| Object | HD Radio |
—
|
NE NERFINISHED |
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: HD Radio | Statement: [KUOW-FM, hasDigitalBroadcast, HD Radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalBroadcast Context triple: [KUOW-FM, hasDigitalBroadcast, HD Radio]
-
A.
hasDigitalSignal
chosen
Indicates that an entity possesses, carries, or is associated with a digital (discrete-valued) signal.
-
B.
hasDigitalTransition
Indicates that an entity undergoes or is associated with a shift from analog or traditional forms to digital technologies, processes, or formats.
-
C.
hasDigitalSubchannels
Indicates that a broadcasting entity provides one or more additional digital subchannels alongside its primary digital channel.
-
D.
hasDigitalEncoding
Indicates that one entity is represented, stored, or expressed using a specific digital code or encoding scheme provided by another entity.
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 1, 2026, 12:18 a.m.