Triple
T32363302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roses (Imanbek Remix) |
E826922
|
entity |
| Predicate | vocalTreatment |
P118708
|
FINISHED |
| Object | pitched-down vocals |
—
|
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: pitched-down vocals | Statement: [Roses (Imanbek Remix), vocalTreatment, pitched-down vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalTreatment Context triple: [Roses (Imanbek Remix), vocalTreatment, pitched-down vocals]
-
A.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
B.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
-
C.
vocalEffects
chosen
Indicates that one entity applies or produces specific modifications, enhancements, or stylistic effects on another entity’s vocal sound or performance.
-
D.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
E.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 12:50 a.m.