Triple
T32114190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Dynamic Digital Sound |
E820193
|
entity |
| Predicate | lowFrequencyEffectsChannel |
P27671
|
FINISHED |
| Object | subwoofer |
—
|
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: subwoofer | Statement: [Sony Dynamic Digital Sound, lowFrequencyEffectsChannel, subwoofer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowFrequencyEffectsChannel Context triple: [Sony Dynamic Digital Sound, lowFrequencyEffectsChannel, subwoofer]
-
A.
lowReCharacteristic
Indicates that the subject has a low characteristic related to electrical resistance (Re), such as low resistance or a low real part of impedance.
-
B.
hasLFEChannels
chosen
Indicates that an entity includes or is associated with one or more Low-Frequency Effects (LFE) audio channels.
-
C.
hasLowerFrequencyIn
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
D.
audioEffect
Indicates that one entity applies or represents an audio processing effect that modifies the sound characteristics of another entity.
-
E.
soundFrequencyRange
Indicates the range of sound frequencies within which the related entity operates, is effective, or is characterized.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b906a92c819096335394dd7f767e |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.