Triple
T16501070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AM |
E400799
|
entity |
| Predicate | audioBandwidthLimit |
P48289
|
FINISHED |
| Object | about 5 kHz to 10 kHz in typical broadcasting |
—
|
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: about 5 kHz to 10 kHz in typical broadcasting | Statement: [AM, audioBandwidthLimit, about 5 kHz to 10 kHz in typical broadcasting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioBandwidthLimit Context triple: [AM, audioBandwidthLimit, about 5 kHz to 10 kHz in typical broadcasting]
-
A.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
B.
usesChannelBandwidth
Indicates that one entity consumes or occupies a portion of the available bandwidth on a communication channel.
-
C.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
D.
supportsBandwidths
chosen
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
E.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e4ddc88819081fedb726add3e96 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.