Triple
T34721718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby S noise reduction |
E1000933
|
entity |
| Predicate | signalDomain |
P181550
|
FINISHED |
| Object | audio |
—
|
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: audio | Statement: [Dolby S noise reduction, signalDomain, audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalDomain Context triple: [Dolby S noise reduction, signalDomain, audio]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
signalReach
Indicates the extent or range over which a signal can be effectively transmitted or received between entities.
-
C.
signalOrigin
Indicates that one entity is the source or starting point from which a signal is generated or transmitted to others.
-
D.
sensingDomain
Indicates the domain or context within which a sensing process, capability, or activity operates or is applicable.
-
E.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.