Triple
T11899953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call You Mine |
E283122
|
entity |
| Predicate | usesVocalEffects |
P79162
|
FINISHED |
| Object | vocal processing |
—
|
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: vocal processing | Statement: [Call You Mine, usesVocalEffects, vocal processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVocalEffects Context triple: [Call You Mine, usesVocalEffects, vocal processing]
-
A.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
B.
usesVocalOverdubbing
Indicates that one entity applies vocal overdubbing to another entity, layering additional recorded vocals over an existing audio track.
-
C.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
D.
voiceEffectsBy
chosen
Indicates that one entity applies or produces voice-related effects that modify or transform the voice of another entity.
-
E.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd16433881909befca9774bdaab4 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.