Triple
T16323668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBZZ |
E396359
|
entity |
| Predicate | audioStreaming |
P122712
|
FINISHED |
| Object | online streaming available |
—
|
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: online streaming available | Statement: [WBZZ, audioStreaming, online streaming available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioStreaming Context triple: [WBZZ, audioStreaming, online streaming available]
-
A.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
B.
streamingRecord
Indicates that an entity maintains a record or log of streaming activity or streamed content associated with another entity.
-
C.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
D.
audioProcessing
Indicates that one entity performs operations to analyze, modify, or transform audio data associated with another entity.
-
E.
audioFocus
Indicates that one entity has priority or control over audio playback or attention relative to other potential audio sources.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b82fe88190a448597b7827f859 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.