Triple
T31368753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cvalda |
E800087
|
entity |
| Predicate | usesSoundDesign |
P155033
|
FINISHED |
| Object | factory noises |
—
|
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: factory noises | Statement: [Cvalda, usesSoundDesign, factory noises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSoundDesign Context triple: [Cvalda, usesSoundDesign, factory noises]
-
A.
hasSoundDesignStyle
Indicates a relationship where an entity is characterized by or associated with a particular style or approach to sound design.
-
B.
soundDesignBy
Indicates that the sound design for a work (such as a film, game, or performance) is created or supervised by a particular person or entity.
-
C.
soundDesignFor
Indicates that one entity is responsible for creating or shaping the audio or soundscape used in another entity (such as a work, scene, or production).
-
D.
usesSound
chosen
Indicates that one entity employs or relies on sound as a means or tool in relation to another entity or context.
-
E.
soundDesignFocus
Indicates a relationship where the primary emphasis or attention is placed on the creation, manipulation, or arrangement of sounds within an audio or media 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 9:18 p.m.