Triple
T25932774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSP |
E653475
|
entity |
| Predicate | commonlyProcesses |
P104012
|
FINISHED |
| Object | audio signals |
—
|
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 signals | Statement: [DSP, commonlyProcesses, audio signals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyProcesses Context triple: [DSP, commonlyProcesses, audio signals]
-
A.
typicalProcess
chosen
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
-
B.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
broaderProcess
Indicates that one process encompasses, includes, or provides the larger context for another, more specific process.
-
D.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
E.
primaryProcess
Indicates that one process is the main or most fundamental process in relation to another process or within a given system or context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 22, 2026, 8:37 a.m.